Back to troubleshooting
Cron troubleshooting
cron
timezone
utc
dst

Cron job running at the wrong time

Fix cron jobs that run at unexpected times because of UTC, server timezones, or daylight saving time.


Timezone mistakes are one of the most common cron problems.

What to check

  • The server timezone.
  • The scheduler platform timezone.
  • Whether the platform always uses UTC.
  • Daylight saving time transitions.
  • Whether logs are shown in UTC or local time.

AWS EventBridge and GitHub Actions scheduled workflows are UTC-based. Linux cron often uses server local time. Kubernetes depends on cluster behavior and configuration.

Related cron resources

Blog
Timezones
Cron Timezone Mistakes

Avoid common cron timezone mistakes across Linux servers, containers, AWS EventBridge, Kubernetes, and CI systems.

Open
Blog
Timezones
Cron Timezones Explained

Understand how cron timezones work across Linux, containers, AWS EventBridge, Kubernetes, and CI systems.

Open
Platform
AWS EventBridge
AWS EventBridge cron guide

Use AWS EventBridge cron and rate expressions safely, including UTC behavior, ? syntax, and year fields.

Open