For those with a non-“smart” alarm or watch, this Sunday (November 2nd, 2025) may be the time to fall back an hour. It’s also a time developers watch for odd errors…
Developer Jon Jensen noted that there are some serious issues with Cron when timed for 2:00 or 3:00 sharp: He “saw two cron jobs run something like once per second between 3:00 and 3:01 when the most recent daylight savings time began. Thus they ran about 60 times, stepping all over each other and making a noisy mess in email. No serious harm was done, but that’s only because they were not tasks capable of causing serious harm.“
There’s also the issue with certain databases with any date between 02:00:00 and 03:00:00 on certain days where the clock moved forward an hour… In order to fix website 500 errors one must go and find these dates and adjust them to a time that “actually exits”, not within the skipped hour… ask me how I know 🙂