Reference
Schedule
The Schedule trigger runs a workflow on a timer, on its own with no input — on a simple interval or a cron expression.
Schedule
Run frequencyEvery X Minutes
Interval (minutes)-
Schedule
Pick how often it runs:
- Every X minutes — a minute interval (1–1440)
- Hourly — a set minute each hour
- Daily — a set time each day
- Weekly — a set day and time each week
- Monthly — a set day and time each month
For finer control, use a cron expression:
0 9 * * 1-5— weekdays at 9 AM*/15 * * * *— every 15 minutes0 0 1 * *— the first of each month
Cron expressions and intervals are evaluated in the configured timezone, which defaults to UTC.
Activation
A schedule is tied to deployment:
- Deploy — the schedule becomes active and starts running
- Undeploy — the schedule is removed
- Redeploy — the schedule is recreated from the current configuration
A schedule only runs once the workflow is deployed. Configure the trigger, then deploy from the toolbar.
Automatic disabling
A schedule disables itself after 100 consecutive failures, to stop runaway errors. A warning badge appears on the block and it stops running; click the badge to reactivate it. The counter resets to zero on any successful run.
A Schedule trigger is an entry point only — it can't receive incoming connections.
Common Questions
Yes. Schedules are created only when you deploy the workflow. Undeploying removes the schedule, and redeploying recreates it from the current configuration.
The schedule is automatically disabled to prevent runaway errors, and a warning badge appears on the block in the editor. Click the badge to reactivate it. The failure counter resets to zero on any successful run.
Yes. The configuration includes a timezone, and both cron expressions and simple intervals are evaluated relative to it. It defaults to UTC.
If a run hits a rate limit (HTTP 429), the schedule retries after a 5-minute delay rather than counting it as a failure.
Yes. Deployment creates a separate schedule record for each schedule block, and each runs independently with its own expression and failure counter.
The running workflow completes, but no new runs are triggered. Before each fire, the schedule checks that the workflow is still deployed and the schedule record still exists.