Something wrong with this tool?
About Cron Next Runs Online
This tool takes a cron expression and predicts the next N execution times (typically 10-50). It works for standard cron syntax and most popular variants (Quartz, Jenkins, Vixie), giving you a concrete sense of when your scheduled job will actually run.
Sometimes a cron expression looks right but the actual execution times are off — daylight saving transitions, timezone confusion, weird month/week interactions can all surprise you. Seeing the next runs explicitly prevents these surprises.
Use it alongside the cron explainer to validate both the meaning and the schedule of any expression before deploying. Most production incidents from cron mistakes are catchable in 60 seconds with these two tools.
How to use this tool
How to peek the next firings of a cron expression
Cron expression
"Cron (5 fields)" accepts a classic 5-field cron string: `minute hour day-of-month month day-of-week`. Whitespace between fields is normalised. Six- or seven-field formats (with seconds or years) aren't parsed here.
How many
"How many" defaults to 5 (max 24). Each row returned is the next scheduled time after `now`, expressed in UTC ISO format. Want server-local time? Convert downstream with your locale formatter.
Press Run
Result returns `nexts` — an array of ISO timestamps. The previewer iterates one minute at a time so it works for any field combination, including `*/15 * * * *` or `0 9 1,15 * 1-5`.
What "now" means
The reference time is the server clock when you press Run, not your local browser clock. If you need a different starting point, you'd need to fork the tool or use a real cron library that takes a `fromDate` argument.