Timezone-Safe Cron Scheduling Without Missed Jobs

Timezone-Safe Cron Scheduling Without Missed Jobs

Cron expressions have no timezone field. They run in whatever timezone the server (or scheduler) is set to -- usually UTC. This causes real production incidents when developers assume local time.

The Classic Trap

You want a daily report at 9:00 AM New York time. You write:

0 9 * * *

But the server runs UTC. This fires at 9:00 AM UTC = 4:00 AM EST (winter) or 5:00 AM EDT (summer). Your report arrives before anyone is awake, and the time shifts with DST.

The DST Problem

Daylight Saving Time creates two specific failure modes:

Spring forward (2:00 AM → 3:00 AM): A job scheduled at 0 2 * * * never runs that night. The 2:00 AM hour does not exist.

Fall back (2:00 AM → 1:00 AM): A job scheduled at 0 1 * * * runs twice. The 1:00 AM hour happens twice.

This affects the US, EU, and ~70 other countries. If your cron job is idempotent, double-runs are harmless. If it sends emails or charges credit cards -- you have a problem.

Solutions

1. Always Store and Run in UTC

The simplest fix: set all cron expressions in UTC and convert for display.

# 9:00 AM ET = 14:00 UTC (during EST) or 13:00 UTC (during EDT)
# Pick one and accept 1-hour drift, or maintain two expressions
0 14 * * *

2. Use CRON_TZ (Supported by systemd, Kubernetes, many schedulers)

# systemd timer
CRON_TZ=America/New_York
0 9 * * *

# Kubernetes CronJob
apiVersion: batch/v1
kind: CronJob
metadata:
  name: daily-report
spec:
  schedule: "CRON_TZ=America/New_York 0 9 * * *"
  jobTemplate:
    spec:
      template:
        spec:
          containers:
          - name: report
            image: report-runner:latest

3. Use IANA Timezone Names, Never Offsets

# GOOD
CRON_TZ=America/New_York
CRON_TZ=Europe/Berlin

# BAD -- does not handle DST
CRON_TZ=EST         # always -5, ignores EDT
CRON_TZ=UTC-5       # same problem

4. Avoid the 1:00-3:00 AM Window

If you cannot use CRON_TZ, schedule jobs outside the DST transition window (1:00-3:00 AM local). Jobs at 4:00 AM local or later are safe.

Verify Before Deploy

Paste your cron expression into the Cron Validator to see the next 5-10 fire times and confirm they align with your expectations. Check both January (standard time) and July (daylight time) dates.

Related