Write a schedule
Choose a format that fires when you want, and understand what happens after downtime or a clock change.
Schedule formats
| Format | Example | Notes |
|---|---|---|
| Interval | every 15m, every 2h |
Counts elapsed time, not clock positions. |
| Daily | daily 07:30 |
Follows the configured time zone. |
| Weekly | a weekday plus a time | Follows the configured time zone. |
| Five-field cron | 30 8 * * 1-5 |
Advanced mode; kept as written. |
The Advanced mode preserves a five-field cron expression as you typed it, including values the builder cannot represent.
Active hours
An active-hours window such as 5-21 keeps a job quiet outside those hours. Overnight windows such as 22-5 work too, and windows use whole hours only, so minutes are not accepted.
A run that falls outside the window is deferred until later today.
When a run is due
The scheduler looks for due work every 30 seconds by default, so a new or changed schedule may take about half a minute to apply.
After downtime, a five-field cron schedule may run its most recent missed occurrence within the catch-up window. It never replays a backlog: daily and weekly schedules do not replay missed days, and intervals do not replay missed ticks.
Daily, weekly and cron schedules follow the clock in the configured time zone. During the autumn clock change a repeated scheduled time runs once, and a time skipped by the spring change does not run that day.
Weekdays and cron fields
Weekly schedules accept weekday abbreviations from sun through sat.
A five-field cron expression supports wildcards, single values, ranges, steps, comma-separated lists, and named months and weekdays. Sunday may be 0 or 7. When both the day-of-month and the day-of-week fields are restricted, either matching field is enough.