Schedule triggers run workflows automatically at a set time or interval. Use them for recurring tasks such as hourly data ingests, nightly reports, or monthly audits.
| Schedule type | When to use |
|---|---|
Run at a specific time on days you define: every day, weekdays only, business days based on a calendar, or any custom scheduling pattern. | |
Run repeatedly at a fixed interval, for example, every 10 minutes or every hour. Combine with a scheduling rule to restrict execution to specific days. | |
Run on advanced scheduling patterns not covered by fixed time or time interval. |
For all schedule types, verify the schedule before saving by selecting Next scheduled executions in the trigger configuration.
If multiple workflows send DQL queries, API calls, or requests to an external system, stagger their start times by a few minutes, for example, 00:00, 00:03, and 00:07. Pinning all workflows to the same start time creates a burst of concurrent requests that can overload the target.
The Fixed time trigger starts at a specific time of day. By default, it starts every day, but you can attach a scheduling rule to limit it to specific days, for example, weekdays only or business days based on a business calendar.
The Time interval trigger starts repeatedly at a fixed interval. You can optionally restrict it to an active period within the day, or attach a scheduling rule to limit it to specific days.
The Cron schedule trigger starts according to a cron expression. Use it for advanced scheduling patterns not covered by fixed time or time interval. Cron expressions follow standard cron syntax based on the Debian cron format and are time-zone-aware. For DST transition behavior. For more information, see Daylight saving time.
*, ,, -, */n, n/m. Six-field (Quartz) expressions and the ? wildcard are not supported.Scheduling rules let you control on which days a fixed time or time interval trigger starts, using criteria such as weekdays, days of the month, or business days from a business calendar. Each environment includes a default calendar; you can create additional ones to model different holiday schedules for teams in different countries. To skip specific dates, such as public holidays, without changing the main schedule, add them as custom holidays in a business calendar and use a rule that filters to working days only.
When the clock changes for daylight saving time (DST), how your schedule behaves depends on whether it is interval-based or time-based.
Time interval trigger, and Cron schedule trigger with a wildcard in the hour or minute field always run at the configured interval, regardless of clock changes.
If you select the Don't run before or Don't run after option for a Time interval trigger:
Fixed time trigger, and Cron schedule trigger run at a specific hour and minute on a set clock time.