Does the five-field Cron parser support seconds or years?

This parser accepts only the 5 fields for minute, hour, day of month, month, and day of week. Minutes range from 0 to 59 and hours from 0 to 23; there are no seconds or year fields. Expressions from Quartz may also use unsupported special characters. Check the source dialect before adapting an expression, because removing a column does not necessarily preserve its scheduling meaning.

How do I write a Cron expression that runs every five minutes?

The five-field expression */5 * * * * matches every 5 minutes within each hour. Its minute values are 0, 5, 10, and so on through 55, and this tool searches from the minute after the chosen starting instant. Select the intended time zone before comparing the results. A displayed local time is not automatically the same as the time zone configured on the server running the task.

Does Cron use zero or seven to represent Sunday?

This parser accepts both 0 and 7 for Sunday. When day of month and day of week are both restricted, it uses an OR match between those conditions. The tool returns at most 20 execution times and searches up to 8 years ahead. Reaching either limit does not establish that the schedule ends permanently; it only describes the bounded preview generated for the selected starting time.

Cron parser

Compute the next N runs of a standard 5-field cron expression

Computed on this site’s server

Enter five cron fields, choose a time zone and result count, then calculate. This previews times; it does not create, run or host scheduled jobs.

Enter a cron expression to compute the next runs.

Example

Input

*/15 9-17 * * 1-5

Example result

09:00, 09:15, 09:30, 09:45, …, 17:45

Every 15 minutes during hours 9 through 17, Monday to Friday, in the selected zone. The range includes 17:45.

Technical details & limits

Fields are minute, hour, day of month, month and weekday; seconds and years are absent. Both 0 and 7 mean Sunday. Restricted day-of-month and weekday fields use OR matching. Only numbers and * / , - are supported, not Quartz ? L W # or month names. Search starts after the current minute, covers up to eight years and returns at most 20 runs.

About this tool

Parse five-field cron expressions and list upcoming runs in a selected time zone, with ISO 8601 and Unix-second output. Supports wildcards, steps, lists and ranges for checking recurring schedules.

Use cases

Sanity-check a crontab you just wrote — when will it actually fire?
Debug a job that has not run all day — often day-of-month and weekday are both restricted with the wrong semantics.
Move a cron to a new time zone and confirm the trigger times still fit the intent.

How to use

Enter a five-field Cron expression, such as */15 9-17 * * 1-5.
Pick the time zone the schedule should be evaluated in.
Pick how many upcoming runs to list (up to 20).

Input & output

Input: A standard 5-field cron string. No L / W / # / weekday names.
Output: The next N fire times in the chosen zone as local time, ISO 8601 and Unix timestamp.
Limits: Search window is fixed at 8 years — beyond that, an unmatched expression returns “no runs in the next 8 years”.

Notes

When both day-of-month and weekday are restricted, Vixie cron uses OR (either match fires). This differs from Quartz — worth knowing.

FAQ

Does the five-field Cron parser support seconds or years?: This parser accepts only the 5 fields for minute, hour, day of month, month, and day of week. Minutes range from 0 to 59 and hours from 0 to 23; there are no seconds or year fields. Expressions from Quartz may also use unsupported special characters. Check the source dialect before adapting an expression, because removing a column does not necessarily preserve its scheduling meaning.
How do I write a Cron expression that runs every five minutes?: The five-field expression */5 * * * * matches every 5 minutes within each hour. Its minute values are 0, 5, 10, and so on through 55, and this tool searches from the minute after the chosen starting instant. Select the intended time zone before comparing the results. A displayed local time is not automatically the same as the time zone configured on the server running the task.
Does Cron use zero or seven to represent Sunday?: This parser accepts both 0 and 7 for Sunday. When day of month and day of week are both restricted, it uses an OR match between those conditions. The tool returns at most 20 execution times and searches up to 8 years ahead. Reaching either limit does not establish that the schedule ends permanently; it only describes the bounded preview generated for the selected starting time.

Related tools

Cron parser · Compute the next N runs of a standard 5-field cron expression — Cron parser — Tool illustration · dayeku.com