What the explainer reads

The parser accepts standard five-field expressions, the common macros (@hourly, @daily, @weekly, @monthly, @yearly), and comments after the schedule. It translates each field independently, then combines them into one sentence. That combination step is where most manual explanations go wrong: “every 15 minutes between 9 and 5 on weekdays” is very different from “every 15 minutes, and also between 9 and 5 on weekdays.”

text
*/15 9-17 * * 1-5
→ At every 15th minute past every hour from 9 through 17 on every day-of-week from Monday through Friday.

0 0 1 * *
→ At 00:00 on day-of-month 1.

Field-by-field breakdown

Every valid expression is shown as a five-row table: the raw field, the parsed values, and the meaning. Use that table when an expression is almost right but fires at the wrong time — usually one field is off by one, or a step is anchored at the wrong starting value.

  • Minute 5 means minute 5 of every hour, not “every 5 minutes”. The latter is */5.
  • Hour */2 means every two hours starting at 00:00 — 00:00, 02:00, 04:00 — not a random two-hour gap.
  • Day-of-week 1-5 is Monday to Friday only if Sunday is 0. In Quartz, 1 is Sunday, so the same string means Sunday to Thursday.
  • A trailing * is not optional: a four-field expression is rejected by most cron daemons.

Why an English description helps

Most production cron mistakes are not syntax errors; they are semantic ones. A schedule that passes validation can still run 24 times a day instead of once. Reading the sentence aloud — “at 2:30 AM on the 1st of every month” — catches the mismatch between intent and expression before it reaches a server.

Check before you change a running job

If you are editing a live crontab, copy the old line and the new line into the explainer and compare the next five run times side by side. A job that shifts from Sunday to Monday can silently break downstream reports even though both expressions are valid.

The explainer uses the same library as the generator, so descriptions and next-run previews stay consistent across the site.