Field by field
0 0 * * 1 reads: At 00:00, on Mondays.
| Field | Value | Selects |
|---|---|---|
| Minute | 0 | 0 |
| Hour | 0 | 00:00 |
| Day of month | * | any day of the month |
| Month | * | every month |
| Day of week | 1 | Monday |
Worth knowing
1is Monday. Midnight Monday UTC is still Sunday evening across the Americas.@weeklyis not this schedule: it runs on Sunday,0 0 * * 0.
Variations
0 9 * * 1Mondays at 09:00Explain it0 0 * * 1,4Mondays and Thursdays at midnightExplain it
The same schedule elsewhere
crontab
0 0 * * 1 /path/to/job.sh
Runs in the machine's local timezone. crontab -e to edit.
GitHub Actions
on:
schedule:
- cron: "0 0 * * 1"Always UTC. Nothing more often than every 5 minutes, and runs can start late when GitHub is busy.
Kubernetes CronJob
spec: schedule: "0 0 * * 1" timeZone: "Asia/Kolkata"
timeZone needs Kubernetes 1.27 or later; without it the controller's zone applies, usually UTC.
Spring @Scheduled
@Scheduled(cron = "0 0 0 * * MON")
Six fields: seconds come first. Days are written as names, which Spring and cron read alike.
Quartz
0 0 0 ? * MON
One of day-of-month and day-of-week must be ?. Quartz counts days 1-7 from Sunday, so names are safer than numbers.
AWS EventBridge
cron(0 0 ? * MON *)
Six fields, the last one the year. UTC unless the schedule sets a timezone. Days count from Sunday, as in Quartz.
systemd timer
[Timer] OnCalendar=Mon *-*-* 00:00:00 Persistent=true
Persistent=true runs a job that was missed while the machine was off, once it is back.