§ 10.1The five fields
| Field | Allowed | Names |
|---|---|---|
| Minute | 0–59 | |
| Hour | 0–23 | |
| Day of month | 1–31 | |
| Month | 1–12 | JAN–DEC |
| Day of week | 0–6 (0 = Sunday; 7 also accepted) | SUN–SAT |
Each field takes * (any), a list 1,15, a range 1-5, or a step */10 or 0-30/5.
§ 10.2The day-of-month trap
When both day of month and day of week are restricted, standard cron runs when either matches. 0 9 1 * MON means “9 AM on the 1st of the month and also every Monday”, not “the 1st, if it is a Monday”. The next-runs list above follows this rule, so you can see it happen.
§ 10.3Common schedules
| Expression | Runs |
|---|---|
*/5 * * * * | Every 5 minutes |
0 * * * * | Every hour, on the hour |
0 0 * * * | Daily at midnight |
30 9 * * 1-5 | Weekdays at 9:30 AM |
0 0 1 * * | First day of every month |
0 3 * * 0 | Sundays at 3 AM |
§ 10.4Other cron flavors
Quartz (Java) and some cloud schedulers use 6 or 7 fields with seconds first, and ? for “no specific value”. AWS EventBridge uses 6 fields with a year. This tool reads the classic 5-field format used by crontab, Kubernetes CronJobs and GitHub Actions — note that GitHub Actions schedules run in UTC by default.
§ 10.QQuestions
What time zone does cron use?
The server’s time zone — usually UTC on cloud machines. The next-runs list here uses your device’s time zone.
How do I run a job every 90 minutes?
A single cron line can’t; use two lines (0 0-21/3 * * * and 30 1-22/3 * * *) or a scheduler that supports intervals.
§ 10.RReferences
Last reviewed 2026-10-14.