Cron Expression Explainer
Parses the actual expression — including ranges, steps, lists, and named months/days — and computes real upcoming run times rather than matching against a few hardcoded examples.
Supported cron syntax
Each of the 5 fields accepts a wildcard (*), a single value, a range
(1-5), a step (*/15 or 1-30/5), or a comma-separated list
combining any of those (1,15,30-45/5). Months and weekdays also accept 3-letter
names — JAN-DEC and SUN-SAT — case-insensitively.
Why does a day sometimes run even though "day-of-month" doesn't match?
This is a genuine cron quirk, not a bug: when both day-of-month and day-of-week are
restricted (neither is *), a day matches if either field matches —
not both. So 0 0 1 * MON runs on the 1st of every month and every Monday,
not only on Mondays that happen to fall on the 1st. If only one of the two fields is restricted,
it behaves as you'd expect and only that field constrains the match.
Why didn't it find any upcoming runs?
Some expressions describe a date that can never occur — for example, day-of-month 30 combined with month February. This tool searches up to 5 years ahead before giving up, so if nothing is found, the expression likely describes an impossible or extremely rare combination worth double-checking.