Question 1

What format does this cron expression parser use?

Accepted Answer

The parser adheres to standard 5-field POSIX / Vixie cron syntax: minute (0–59), hour (0–23), day of month (1–31), month (1–12), and day of week (0–6, where 0 is Sunday).

Question 2

What do symbols like *, /, -, and , mean in cron expressions?

Accepted Answer

An asterisk (*) represents every possible value; a slash (/) specifies step increments (e.g. */15 means every 15 minutes); a hyphen (-) defines an inclusive range (e.g. 1-5); and a comma (,) separates distinct values in a list (e.g. 1,15,30).

Question 3

How are day-of-month and day-of-week handled when both are specified?

Accepted Answer

In standard POSIX cron, if both day-of-month and day-of-week are restricted (neither is *), the schedule triggers when either condition matches (an OR relationship), not both.

Question 4

In what timezone are the next 8 scheduled dates calculated?

Accepted Answer

Execution times are calculated using your local computer or device's current timezone. When scheduling tasks on cloud servers, ensure you account for your server's system timezone (often UTC).

Question 5

Does this tool support 6-field cron expressions with seconds?

Accepted Answer

No. This tool specifically targets standard 5-field operating system cron (Linux, macOS crontab). 6-field expressions (such as those used by Java Spring or Quartz schedulers) include seconds as the first field.

Explain a cron schedule in plain English

Cron expression simulation

Frequently asked

Feedback, bugs & custom requests

Related tools