The folded hour · Sunday 1 November 2026

Did your scheduled job run twice, loop or skip when the clocks went back?

On Sunday 1 November the US and most of Canada set their clocks back, so 01:00 to 01:59 happened twice. Choose your scheduler and one job. You get our guides' answer for that job, what to check in its runs since then, and the smallest change we tested.

What broke when 01:00 came twice: four programs we reproduced.

Update, 2 November: by 15:32 UTC we had found no report from 1 or 2 November that contradicts this page's answers for n8n, APScheduler and LiteLLM, Camunda 7, Operaton and CIB seven, or Spring. We did not search for Kubernetes CronJob reports. The n8n, APScheduler, Camunda and Spring guides list where we looked.

1 Scheduler
2 Version
3 Time zone the scheduler uses

Not your server's location: the zone set for the scheduler or its process.

4 The job

What the guide says