Free tool
Parse Unix, Quartz, Spring, EventBridge, GitHub Actions, Kubernetes, and Vercel schedules. See the next runs in your timezone and flag the DST hours that skip or fire twice.
A plain-language explanation is useful, but production schedules fail in the details: the target dialect, the timezone that interprets the wall clock, and the next concrete run times. Zeitful shows the actual queue of upcoming runs so you can spot a misplaced weekday number or an accidental UTC assumption before it ships.
Local-time cron jobs do not behave like fixed intervals. A 02:30 job can disappear during spring forward, while fall back can repeat the same wall-clock hour. The DST badges call out those transitions directly in the run list, which is where teams usually catch the problem fastest.