Schedule Expressions v2

The Runtime supports Daily, Weekly, Monthly, and Cron schedules. Date and time should be set according to the time zone set on the Site.

Windowed schedules

Daily, Weekly, and Monthly Methods share these settings:

Setting	Contract
StartTime	Inclusive local start time in HH:mm:ss.
EndTime	Inclusive local end time in HH:mm:ss. An end before the start creates a window across midnight.
Interval	Positive interval value.
IntervalType	Minutes or Hours.
SingleInstance	When true, skip a due slot if the same Workflow already has an active instance.

Weekly schedules require one or more day values from Sunday through Monday. For a window across midnight, times after midnight still belong to the window that started on the selected previous day.

Monthly schedules require one or more days from 1 through 31 or Last. Select months from January through December. A numeric day that does not exist in a selected month does not create an occurrence; Last resolves to that month's actual last day.

Cron schedules

Cron uses six fields and includes seconds:

second minute hour day-of-month month day-of-week

For example, 0 */15 * * * * is due every 15 minutes at second zero. Cron evaluation uses the Site time zone, including its daylight-saving rules.

The expression must parse and produce a future occurrence. Publish rejects a schedule that does not produce one.

Dispatch behavior

The scheduler checks due work every 30 seconds on the primary active Cluster and sends the Workflow to its configured execution Cluster. This coordination interval means actual start time may be slightly later than configured time.

When debuging a Workflow, time-based Triggers are treated as having fired immediately.

See also

See Create a Scheduled Workflow and Triggers.