Scheduling Components

Applies to

• Collections

• Data Targets

• Workflows

Schedule settings are on the Advanced tab.

Custom Schedule

The schedule field allows for custom schedules to be built. While the most commonly used scheduling options are available within Presets, anything outside of those can be customized (e.g. running a workflow every 5 minutes between the hours of 1pm - 2pm every weekday).

The scheduler utilizes cron for customization. The format will be five sections separated by spaces ( * * * * * ). The first section represents minute; the second represents hour; the third represents day (month); the fourth represents month; and the fifth represents day (week). Visit Crontab.guru - The cron schedule expression editor for more information

Examples

5 5 5 5 5 - (At 05:05 AM, on day 5 of the month, and on Friday, only in May)

0-55/5 13-14 * * 1-5 - (Every 5 minutes, minutes 0 through 55 past the hour, between 01:00 PM and 02:59 PM, Monday through Friday)

0 9,12,16 1,10,20 1,2,3 * - (At 09:00 AM, 12:00 PM and 04:00 PM, on day 1, 10, and 20 of the month, only in January, February, and March)

When the cron expression includes a time of day, a Time Zone field will appear in the Cron editor. If your schedule runs on an interval with no specific time (e.g. every 30 minutes), the Time Zone field will not appear because it is not applicable in that context.

Time Zone

An optional Time Zone field is available on the schedule configuration. When a time zone is selected, the schedule runs according to that time zone and automatically adjusts for daylight saving time — a schedule set for 1:00 PM Eastern will continue to run at 1:00 PM Eastern after DST transitions, rather than shifting by an hour.

When using a preset that includes a specific time (e.g. Every day at a specific time or On a specific day of the week), the Time Zone field appears alongside the time selector. Set the time zone before entering the time so that your selection is interpreted correctly. 

When no time zone is selected, the schedule runs in UTC as before. Existing schedules are not affected unless a time zone is explicitly set.

For newly created schedules, the Time Zone field defaults to the browser's detected location time zone.

The Schedules table on the dashboard displays run times in your local time. Hovering over a scheduled time shows the time in the configured time zone along with its UTC offset (e.g. EST, UTC-05:00).

Scheduling Presets

1. Every X minutes

2. Every Hour

3. Every day at a specific time

4. On a specific day of the month

5. On a specific day of the week

Every X Minutes

Use to schedule a job for multiple times a day.

Select an interval in minutes, between 1 and 59.

Every Hour

Use to schedule at the top of every hour

Every day at a specific time

Use for scheduling jobs to run once a day. When configuring this preset, a Time Zone field appears alongside the time selector. Set the time zone first to ensure the time you enter is interpreted in the correct time zone. 

On a specific day of the month

Use for scheduling once or more per month, at a specific time of day. A Time Zone field appears alongside the time selector for this preset.

On a specific day of the week

Use for scheduling once or more per week. A Time Zone field appears alongside the time selector for this preset. 

Pausing a Schedule

Scheduled jobs can be temporarily paused by setting the Is Paused toggle to True and saving the component. The configured schedule is preserved and can be restarted by setting the Is Paused toggle to False.

Additional Notes

1. Running a job manually does not reset the schedule; a collection set to run every 5 minutes at 1:05, 1:10, 1:15, etc. will continue to run on that schedule even if the collection is run manually at 1:08.

2. Schedules run in UTC by default. To avoid time shifts caused by daylight saving time, select a Time Zone in the schedule configuration. When a time zone is set, the cron expression is evaluated in that time zone and DST transitions are handled automatically. The Schedules table shows run times in your local time; hover over any scheduled time to see the configured time zone and UTC offset. 

3. Workflow, Collection and Data Target schedules are independent. A scheduled workflow will run each associated collection and target in turn. If a collection or target is scheduled as part of a workflow but it also has a schedule configured, it will be run as scheduled by the workflow and again as scheduled by itself. to match its own configuration.