What is Daylight Saving Time (DST)?
Seasonal clock adjustment that shifts local time by one hour, affecting cron job timing.
Definition
Daylight Saving Time is the practice of advancing clocks by one hour during warmer months to extend evening daylight. This creates two annual disruptions: in spring, clocks skip forward (2:00 AM becomes 3:00 AM), and in fall, clocks fall back (2:00 AM occurs twice). Cron jobs scheduled in local timezones during these transition hours may skip, run twice, or shift by an hour.
Simple Analogy
Like a clock that hiccups twice a year — in spring it skips a beat (missing an hour), and in fall it stutters (repeating an hour). Any job timed to that beat gets disrupted.
Why It Matters
DST transitions are a notorious source of scheduling bugs. A job scheduled for 2:30 AM in a US timezone will not run during the spring-forward transition (that time does not exist) and may run twice during the fall-back (that time occurs twice). Critical jobs like billing, backups, or compliance reports can be affected.
How to Verify
Review your cron job's timezone setting and check if that timezone observes DST. Test by checking execution history around DST transition dates (typically March and November in North America, March and October in Europe). CronJobPro handles DST transitions according to the IANA timezone database.
Common Mistakes
Scheduling critical jobs during the 1:00-3:00 AM window when DST transitions occur. Assuming all countries observe DST (many do not, including most of Asia and Africa). Not testing cron behavior during DST transitions and discovering issues in production.
Best Practices
Schedule critical jobs outside the DST transition window (avoid 1:00-3:00 AM local time). Consider using UTC for jobs where exact timing matters more than local convenience. If you must use local time, use IANA timezone names that automatically handle DST rules.
Cron Expression Explainer
Explain a cron expression
Try it free →Frequently Asked Questions
What is Daylight Saving Time (DST)?
Daylight Saving Time is the practice of advancing clocks by one hour during warmer months to extend evening daylight. This creates two annual disruptions: in spring, clocks skip forward (2:00 AM becomes 3:00 AM), and in fall, clocks fall back (2:00 AM occurs twice). Cron jobs scheduled in local timezones during these transition hours may skip, run twice, or shift by an hour.
Why does Daylight Saving Time (DST) matter for cron jobs?
DST transitions are a notorious source of scheduling bugs. A job scheduled for 2:30 AM in a US timezone will not run during the spring-forward transition (that time does not exist) and may run twice during the fall-back (that time occurs twice). Critical jobs like billing, backups, or compliance reports can be affected.
What are best practices for Daylight Saving Time (DST)?
Schedule critical jobs outside the DST transition window (avoid 1:00-3:00 AM local time). Consider using UTC for jobs where exact timing matters more than local convenience. If you must use local time, use IANA timezone names that automatically handle DST rules.
Related Terms
Timezone
The regional time standard that determines when a scheduled job actually fires.
UTC (Coordinated Universal Time)
The global time standard with no daylight saving adjustments, used as the baseline for all timezones.
CRON_TZ
A crontab directive that sets the timezone for schedule interpretation.
Schedule
A defined plan that determines when and how often a job runs.