be me, sysadmin, Sunday morning in March clocks go forward at 02:00 cron job scheduled for 02:30 "monthly reports" that hour does not exist today cron, being clever, runs it at 03:00 or does it? depends on the version in October the opposite: 02:30 happens twice it ran twice customers received two reports the customers found out before I did
The server was in local time because "that is how it was installed". The fix is boring: run servers in UTC, schedule jobs at a time that never falls in the missing or repeated hour, and make the job itself idempotent, so running twice does no harm.