Skip to main content

Recurring schedules

Choose a Recurring trigger when work should start on a calendar. Select a timezone explicitly, such as Europe/Vienna, and review the upcoming occurrences before publishing.

FrequencyConfiguration
DailyA local time.
WeeklyOne or more weekdays and a local time.
MonthlyOne or more days of the month and a local time.
CronFive numeric fields: minute, hour, day of month, month and weekday.

For example, 0 9 * * 1-5 means weekdays at 09:00 in the selected timezone. Cron accepts wildcards, lists, ascending ranges and positive steps. When both day of month and weekday are restricted, both must match. Seconds, named weekdays and embedded timezone overrides are unsupported.

A scheduled run has no triggering record​

The run provides the scheduled time, actual admission time and timezone. It does not implicitly find or loop through records. Turn off the triggering-record link on Task and question steps. Configure any record operation with an explicit record or unique key.

A simple first schedule is Daily at 09:00 → Create Task “Review today's requests” → End.

When an occurrence is skipped​

  • If an earlier run is still open, the next occurrence is skipped. Waiting for approval counts as an open run.
  • An occurrence starting more than five minutes late is skipped.
  • A nonexistent date, such as February 31, is skipped.
  • A local time inside a daylight-saving gap is skipped. If the clock repeats a local time, both occurrences of that ambiguous time are skipped.
  • Re-enabling starts with a future occurrence. The paused period is not replayed.

An admitted run can recover from interruption. A failed run does not by itself pause future occurrences.

Preview, publication and status​

Occurrence preview shows up to five eligible dates, local times and UTC offsets. A sparse or exhausted calendar may return fewer. It creates no schedule or run and does not simulate overlap or outages.

Draft changes have no effect on the live calendar. Publish to apply them. The timezone stays part of the publication even if workspace regional settings change.

Schedule synchronization is asynchronous. A pending status after publication means the saved schedule has not yet been confirmed as applied. Persistent errors belong in Troubleshooting. Pausing stops future admissions; existing runs continue.

For exact calendar syntax and supported horizons, see the recurring-trigger API reference.