Cron Expression Parser: common mistakes and how to fix them
The failure modes that actually happen in practice, what each one looks like in the output, and the concrete fix.
How to use
- Check the input encoding first — a stray byte-order mark or a non-UTF-8 paste corrupts the result before the tool ever runs.
- Look for silent truncation: if the output length is suspiciously round, something was cut off.
- Confirm the option you changed is the one the task needs; a leftover default is the most common cause of a wrong-but-plausible result.
- Re-run with a minimal input you can verify by hand, then add your real data back.
Examples
Explains schedule + next runs.
Input
0 3 * * 1-5
Output — Results
Minute 0 · Hour 3 · Day-of-month * · Month * · Day-of-week 1-5 Next runs: 2026-09-14 03:00 local 2026-09-15 03:00 local 2026-09-16 03:00 local 2026-09-17 03:00 local 2026-09-18 03:00 local 2026-09-21 03:00 local 2026-09-22 03:00 local 2026-09-23 03:00 local 2026-09-24 03:00 local 2026-09-25 03:00 local
Run
Description
Explain cron syntax and compute the next 10 run times.
Related tools
HTTP Status Code LookupSearch all HTTP status codes with meanings and usage notes.User-Agent ParserBreak a User-Agent string into browser, engine and OS.ASCII Character TableInteractive reference of all 128 ASCII codes.Unicode Character LookupInspect code points, blocks and UTF encodings of any character..gitignore GeneratorAssemble a .gitignore from curated stack templates.Base64 EncoderEncode text, JSON, URLs or files to Base64, standard or URL-safe.