Practical guide
How to use Cron Expression Inspector
Cron Expression Inspector checks portable five-field schedules for minute, hour, day of month, month, and day of week. It expands lists, ranges, wildcards, and step values, then previews upcoming runs in the timezone configured on the current device so scheduling mistakes become visible before deployment.
Step by step
- Paste a five-field expression such as 15 9 * * 1-5.
- Validate the fields and read the plain-language field summary.
- Compare the next run times with the timezone and cron implementation used by the real scheduler.
Example
15 9 * * 1-5At minute 15 past hour 9 on Monday through Friday; upcoming runs shown in the device timezoneHow it works
Each field is parsed into an allowed set of numeric values. The preview advances minute by minute through a bounded future window and applies traditional cron day matching, where restricted day-of-month and day-of-week fields match when either one is satisfied.
Important limitations
- Only classic five-field syntax is supported; seconds, years, L, W, #, ?, @daily, and vendor macros are intentionally rejected.
- Cron dialects disagree about day matching, Sunday numbering, daylight-saving transitions, and missed runs.
- The preview uses the device timezone and is not a guarantee that a cloud scheduler has the same timezone or retry policy.
Real workflows
When this tool is useful
Deployment review
Check a scheduled backup, report, cleanup, or integration expression before adding it to a server, container, CI workflow, or cloud scheduler.
Timezone incident
Compare expected wall-clock times with the device timezone when a job appears an hour early, an hour late, duplicated, or missing.
Dialect migration
Identify unsupported seconds, year, question-mark, last-day, weekday, or macro syntax while moving a schedule between platforms.
Review the result
What to check before using the output
Record the exact cron dialect, timezone, daylight-saving policy, concurrency behavior, retry policy, and what happens after downtime. Preview both ordinary dates and the next timezone transition when local civil time is involved.
- Confirm five-field order.
- Match the production timezone.
- Check DOM/DOW semantics.
- Test daylight-saving and missed-run behavior.
Choose the right method
When another tool is better
Use the scheduler's own validator and execution history for production confirmation. Event queues, durable workflows, or application-level scheduling are better when every run must be guaranteed, retried, deduplicated, or audited.
Privacy and browser behavior
The expression is parsed locally and usually contains no secret. Job timing can still reveal internal operational routines, maintenance windows, reporting cycles, or backup policy when shared publicly.
Frequently asked questions
Why is my six-field expression rejected?
Some platforms add a seconds field. This tool deliberately accepts only the portable five-field minute-first form.
What happens during daylight-saving changes?
A local clock time may be skipped or repeated. Confirm the production scheduler's documented behavior and consider scheduling in UTC.
Does 0 0 1 * 1 mean Monday and the first day together?
Traditional cron commonly treats the two restricted day fields as OR, but some services differ. The tool states the rule it uses so you can compare it with your platform.