The Schedule block automatically triggers workflows on a recurring schedule at specified intervals or times.
Schedule Options
Configure when your workflow runs:
- Every X Minutes: Run at minute intervals (1-1440)
- Hourly: Run at a specific minute each hour
- Daily: Run at a specific time each day
- Weekly: Run on a specific day and time each week
- Monthly: Run on a specific day and time each month
Use cron expressions for advanced scheduling:
0 9 * * 1-5 - Every weekday at 9 AM*/15 * * * * - Every 15 minutes0 0 1 * * - First day of each monthActivation
Schedules are tied to workflow deployment:
- Deploy workflow → Schedule becomes active and starts running
- Undeploy workflow → Schedule is removed
- Redeploy workflow → Schedule is recreated with current configuration
You must deploy your workflow for the schedule to start running. Configure the schedule block, then deploy from the toolbar.
Automatic Disabling
Schedules automatically disable after 100 consecutive failures to prevent runaway errors. When disabled:
- A warning badge appears on the schedule block
- The schedule stops executing
- Click the badge to reactivate the schedule
Schedule blocks cannot receive incoming connections and serve as workflow entry points only.
Common Questions
Yes. Schedules are created in the database only when you deploy the workflow. Undeploying removes the schedule, and redeploying recreates it with the current configuration.
After 100 consecutive failures, the schedule is automatically set to a disabled status to prevent runaway errors. A warning badge appears on the schedule block in the editor. You can click the badge to reactivate it. The failure counter resets to zero on any successful run.
Yes. The schedule configuration includes a timezone setting. Cron expressions and simple intervals are evaluated relative to the configured timezone, which defaults to UTC if not specified.
If a rate limit (HTTP 429) is encountered during a run, the schedule automatically retries after a 5-minute delay rather than counting it as a failure.
Yes. The deployment process finds all schedule blocks in the workflow and creates a separate schedule record for each one. Each schedule operates independently with its own cron expression and failure counter.
The currently running workflow will complete, but no new runs will be triggered. When the schedule next tries to fire, it checks that the workflow is still deployed and the schedule record still exists before running.