Cron Parser
| Field | Raw | Reading |
|---|
Next 5 runs
| # | Time | Day |
|---|
About Cron Parser
Handles five-field and six-field expressions, where the sixth is seconds. Asterisks, ranges, lists and steps all work, and months and weekdays accept English abbreviations.
The parser explains each field and then works out the next five run times in your browser's local timezone. That last part is what makes it useful: when you are not sure an expression is right, seeing the actual times settles it.
One trap worth knowing. When both the day-of-month and day-of-week fields are restricted, traditional cron fires if either matches, not both. This follows the traditional reading, same as Linux.
Frequently asked questions
What is the difference between five and six fields?
The sixth is seconds, common in Quartz-style schedulers. Linux crontab uses five.
Does it accept @daily?
No, only standard fields are parsed.
Which timezone does it use?
Your browser's. If the server runs elsewhere, actual firing times will differ.
Why does 0 0 31 2 * produce nothing?
February has no 31st, so that expression never fires. It is a mistake, not a bug.
