Scheduler

Scheduler is a native Workato app that enables users to run recipes at pre-defined intervals. With the scheduler, users can trigger recipes with simple schedules (for example, every hour or every day) or configure complex intervals (for example, every two weeks or only on weekdays).

If your workflow use case is not triggered by events from other applications, use the scheduler to configure a customized schedule.

LONG ACTIONS JOB SEQUENCE

If your recipe has a long action step and job, note that when the action is put on hold, Workato automatically disregards the job sequence. The next job begins to process even if the previous job is not finished and the recipe concurrency is set to 1.

Using the scheduler trigger

Select the New recurring event trigger.

New recurring event trigger

Schedule configuration

Configure your schedule from the input prompts or define a custom schedule with a CRON expression.

Input fields for new recurring event trigger

Input	Description
Time unit	Select the largest time unit. For example, if this recipe runs weekly on Monday and Friday, select Weeks as the time unit.
Trigger every	Define a repeating schedule. The shortest interval is 5 mins.
Additional time configuration Only for Days, Weeks, or Months	If you selected a time unit that is Day or larger, use the additional input fields to define the schedule. Additional configuration includes: Trigger at (hour and minute) Days of the week Days of the month
Cron expression Only for Custom schedule	This advanced option allows you to use CRON expressions to set the custom schedule. Learn more about CRON expressions below.
Timezone	Select the timezone.

Timezone

The scheduled time will be reflected in (GMT-08:00) Pacific Time (US & Canada).

Use the optional input Timezone to change the timezone

Configure custom schedule with CRON expression

Learn how to use CRON in 2 mins

Select Custom schedule as the Time unit.

CRON expression for custom schedule

How to write a CRON expression

CRON expressions follow a fixed and ordered syntax. Every element must be defined and cannot be left blank. Use the wildcard * to represent "all possible values". Learn more about CRON expressions (opens new window).

<Minute> <Hour> <Date> <Month> <Day>

CRON expression example

CRON expression	Examples
0 0 * * *	Everyday at midnight 0000 hrs.
*/10 * * * *	Every 10 mins.
0 0 1 * *	First day of every month at midnight 0000 hrs.
0 0 L * *	Last day of every month at midnight 0000 hrs.
0 0 * * 1,5	Every Monday and Friday at midnight 0000 hrs.
0,30 * * * *	Twice every hour, at 00 mins and 30 mins.
0 9 * * MON#1	First Monday of every month at 0900 hrs.

Actions

The following 3 actions are also supported:

• Get current time

This action returns the specific date and time when this step is executed in a job. This date and time is expressed in UTC, for example, 2017-01-30T05:30:33.479446+00:00.

• Wait for specified length of time

This action allows you to specify the number of seconds the recipe should wait for before proceeding on to the next step.

• Wait until the specified time

This action allows you to specify the time to wait until before proceeding on to the next step. If the time specified is in the past, the recipe immediately proceeds on to the next step.

Setting a dynamic time

To wait until next Monday, 8AM PST before proceeding to the next step, toggle the Time input field to formula mode and set the value to today.beginning_of_week + 7.days + 8.hours. See Date formulas for more examples.

Deprecated Scheduler triggers

The old Scheduler triggers are deprecated. Support for existing recipes using the deprecated triggers will continue. However, users will not be able to configure new recipes using the deprecated triggers.

The deprecated triggers are:

• New scheduled event trigger
• New scheduled event (advanced) trigger

Will my old recipes be affected?

No, the deprecated trigger will continue running as configured. You can continue keeping the recipe running with any disruptions.