For the complete documentation index, see llms.txt. This page is also available as Markdown.

Scheduling workflows

Configure the current recurring schedule options for a published Workflow and understand when they take effect.

A schedule trigger starts the default Published Workflow automatically according to a configured recurrence.

This is Workflow scheduling. It is separate from Control → Schedules, which schedules Agent runs.

Available recurrence options

The current Workflow builder generates a five-field cron expression from two UI modes:

  • Interval: every 5, 10, 15 or 30 minutes, or every 1, 2, 4, 6 or 12 hours.

  • Specific time: a time of day combined with selected weekdays.

There is no free-text cron editor in the builder.

Time zone

Choose from the supported named time zones or use the detected browser zone. The selected IANA-style zone is stored with the schedule and passed to the scheduler, so daylight-saving changes follow that named zone.

When a schedule becomes live

Changing the schedule on a Draft does not alter the current production schedule. The scheduler is synchronised when the version is published and becomes the default.

Scheduled executions are asynchronous and fire-and-forget from the scheduler's point of view. Inspect the resulting Workflow run in Monitoring.

Current limits

The builder does not currently support:

  • sub-minute schedules;

  • a one-off "run at this date and time" schedule;

  • day-of-month or month selection;

  • scheduler-level retry when the scheduled trigger itself fails.

Be careful with every N days

The current "every N days" representation uses a day-of-month cron step. That step restarts at the beginning of each month, so it is not a true continuous every-N-days interval across month boundaries.

If exact rolling cadence matters, do not assume that option provides it.

Last updated

Was this helpful?