Skip to content
Did It Run?
Start Free
← Blog

The clocks fell back last night. Did your jobs run?

Most of the US turned clocks back an hour at 2:00 am today, so 1:00 to 1:59 happened twice. (timeanddate.com)

Three quiet effects to check this morning:

  1. Jobs in the repeated hour. Debian cron says fixed-time jobs in a repeated hour "will not be re-run." Jobs with * in the hour or minute field follow the new time immediately. (Debian cron(8))
  2. UTC schedules. A 0 13 * * * UTC job now lands at 8:00 am in New York instead of 9:00. Nothing failed, but anything expecting it at 9 is now off by an hour.
  3. Next March. Spring forward skips 2:00 to 2:59 entirely.

The fix: move local-time jobs out of 1 to 3 am, and give each a heartbeat in the scheduler's timezone.

Catch clock-change misses, free for 3 watches.