Overview
Parse cron expressions and preview the next run times. Useful for validating schedules before deploying jobs, and for debugging misfiring cron tasks. Runs locally in your browser.
Use cases
- Check whether a cron runs every 5 minutes or at minute 5 (common confusion).
- Preview future run times to validate day-of-week and month fields.
- Debug why a job triggers at unexpected times (timezone vs local time).
Common pitfalls
- Day-of-week numbering differs across systems (0/7 as Sunday). Verify your target runtime’s rules.
- Quartz cron syntax differs from standard cron; features may not parse the same way.
FAQs
5-field vs 6-field cron?
Many systems use 5 fields (min hour day month weekday). Some include seconds as a 6th field. This tool follows the parser rules.
What timezone is used?
Times are displayed in your browser’s local timezone.
Why is my cron not supported?
Some cron features are engine-specific (quartz extensions). If parsing fails, try simplifying to standard cron syntax.
How many next runs are shown?
The UI typically shows a small list of upcoming runs to help you validate schedules quickly.
Examples
Input
*/5 * * * *
Output
Every 5 minutes; next 5 runs