Why Your Cron Job Fires at the Wrong Time: IST, UTC and the Midnight Day Shift
You write 0 21 * * * to run a report at 9 PM. It runs, just not when you expected: at 2:30 AM India time. Nothing is broken. Cron did exactly what you asked, in a timezone you didn't know it was using
Responses
Markdown supported · ⌘↵ to post
Seedance AI
Seedance AI creative notes on video workflows, prompts and original visual examples.
Timezone drift in scheduled jobs has bitten almost every production team at least once. Standardizing all scheduler environments on pure UTC and handling regional offset logic strictly at presentation time prevents so many silent midnight rollover bugs.