Schedules and timing

Three shapes cover the ground: a cron expression, a fixed interval, and a single moment.

Cron

Five fields, in the job's own timezone. Ranges, lists and steps all work, and the form shows the next five runs while the expression is being typed.

*/5 * * * *      every five minutes
0 2 * * *        daily at 02:00
15,45 9-17 * * 1-5   quarter past and quarter to, business hours, weekdays

Clock changes

Wall-clock times hold across a daylight saving change, so a daily 02:00 stays at 02:00. The two awkward days are handled explicitly. A local time the spring change removes is skipped, and a local time the autumn change repeats runs once, at the first occurrence.

Interval

Every N seconds, anchored to the moment the job was created rather than to the last run, so a slow response does not push the schedule later and later.

Timing

A run starts within a few seconds of its scheduled time, not on the second. Delays of up to a minute happen during maintenance or a platform incident. Every run records both the scheduled time and the actual start, and the difference is shown as drift in the job history. Work needing exact-second precision or a guaranteed execution is a poor fit for the service.