Debug a Cron Job That Won't Run
See whether a cron expression actually matches the times you think it does.
At 9:00 AM, Monday through Friday.
- Thu, May 28, 2026, 09:00 AMin 11 hr
- Fri, May 29, 2026, 09:00 AMin 35 hr
- Mon, Jun 1, 2026, 09:00 AMin 4 days
- Tue, Jun 2, 2026, 09:00 AMin 5 days
- Wed, Jun 3, 2026, 09:00 AMin 6 days
💡 Fields are: minute, hour, day-of-month, month, day-of-week. Supports ranges (1-5), lists (1,15), steps (*/15), names (MON, JAN), and macros (@daily). All parsing happens in your browser.
debugging tips
A job "not running" is often a misread schedule — the explanation and next-run list reveal the real timing.
Watch for the day-of-month vs day-of-week rule: when both are set, cron runs if either matches.
Check step values (*/5) and ranges carefully — the field breakdown shows each one.
No data leaves your device.
Hoe dit werk
Hoekom ons gebruik?
Also check out…
Understand a crontab Entry
Decode a line from your Linux crontab into plain E
Check a GitHub Actions Schedule
Verify the cron in your workflow's schedule trigge
Build a Cron Schedule
Experiment with cron fields until the schedule mat
Learn Cron Syntax
Understand how the five cron fields work by exampl