TIME ISN’T ALWAYS LINEAR
Will your scheduled time
exist when the clocks change?
Check a daily or weekly local time across the next year. Find the days with no matching instant — or two of them — before your workflow reaches them.
Clock-change report
Choose your schedule to begin.
First 7 scheduled dates
READ THE RESULT
A clock-time check.
A better question for your scheduler.
Missing time: the local clock skips over your selected time. No UTC instant has that local date and time.
Repeated time: the local clock passes your time twice. Both UTC candidates are shown.
A scheduler may skip, shift, or deduplicate these cases. This tool finds time ambiguity; it doesn’t predict a particular cron engine’s execution policy. It checks local wall-clock schedules, not fixed elapsed-time intervals.
Results use your browser’s timezone database and its projected rules. Update your browser and verify critical schedules against the runtime you deploy. Known 2026 changes for Vancouver, Edmonton, Inuvik, Winnipeg, Casablanca and El Aaiun are checked; incompatible runtime data blocks affected reports. This limited check does not certify other zones. Rule-change source (checked 19 October 2026).
Using this with n8n or cron
Check the timezone configured in your workflow and instance. In n8n, the workflow timezone takes precedence over the instance timezone. Save and publish your workflow after changes, and verify actual executions around a transition.
References: n8n Schedule Trigger · Browser timezone formatting
INDEPENDENT & FREE
Useful tools need a way to stay useful.
There is no paid sponsor today. We’re exploring one clearly labelled placement for a relevant developer service. No affiliate commissions, tracking pixels, or paid ranking.