Schedules

A schedule runs a job at fixed times. Each job has at most one schedule, and a schedule can sit alongside triggers on the same job.

Cron and timezones

Schedules use standard 5-field cron, for example 0 9 * * * for 9am every day. Extended operators such as #, L, and W are not supported.

Every schedule carries a timezone, given as an IANA name like Europe/Berlin and defaulting to UTC. Daylight saving is handled for you: 0 9 * * * in Europe/Berlin stays at 9am local time across the change.

The finest cadence cron allows is every minute. Check the time limits in runs before scheduling a job more often than it can finish.

Overlapping runs are skipped

If a scheduled run is still going when the next scheduled time arrives, that occurrence is dropped rather than queued, and the schedule carries on at the following slot. This applies between scheduled runs only: a trigger event or a manual run can still start while one is in progress.

Pausing and manual runs

A schedule is either Active or Paused. Pausing stops future runs without deleting the schedule, and resuming picks the cadence back up.

You can run a job by hand at any time, whether or not it has a schedule, to test it or to run it once outside its normal cadence.

If your subscription lapses for more than a week, schedules are paused automatically.