Cron every Monday
0 9 * * 1 — Day of week 1 is Monday in Linux cron; this runs every Monday at 09:00. MON works too and is unambiguous everywhere names are allowed.
Runs
Try one
The same schedule in every dialect
| Where | Expression | |
|---|---|---|
| Linux / Unix crontab, Kubernetes, GitHub Actions | 0 9 * * 1 | explain |
| Quartz Scheduler | 0 0 9 ? * MON | explain |
| AWS EventBridge | cron(0 9 ? * MON *) | explain |
Spring @Scheduled | 0 0 9 * * MON | explain |
| Jenkins | 0 9 * * 1 | H calculator |
systemd timer OnCalendar= | Mon *-*-* 09:00:00 | test |
Things to know
- "The first Monday of the month" is not
0 9 1-7 * 1. With both day fields set, Linux cron runs on either, so that line fires on the 1st–7th and on every Monday. Quartz and AWS haveMON#1; in Linux cron, use0 9 1-7 * *and test the weekday in the command. @weeklyis Sunday at 00:00, not Monday. In Jenkins it isH H * * H, a per-job day and time.
Variations
| Expression | Runs |
|---|---|
| 0 0 * * 1 | Monday at midnight |
| 0 9 * * 1,4 | Monday and Thursday at 09:00 |
| 0 9 * * MON | the same schedule, with a name |
How to use this schedule
- Open your crontab with
crontab -e(or the scheduler's config file). - Add a line with the expression followed by the command:
0 9 * * 1 /usr/local/bin/job.sh. Use absolute paths — cron runs with a minimalPATH. - Save. cron picks the change up automatically; check the next run times above, in the time zone your server uses.
- Redirect output if you want to keep it: append
>> /var/log/job.log 2>&1. The crontab line builder assembles the whole line.
FAQ
Is "0 9 * * 1" the same on every server?
The five-field form means the same thing in Linux cron, Kubernetes, GitHub Actions and most libraries. The clock it follows differs:
a Linux server uses its own time zone (or CRON_TZ on cronie), GitHub Actions and AWS EventBridge rules use UTC unless a time zone is configured, and Kubernetes uses the controller's zone unless .spec.timeZone is set.
Why do Quartz and AWS need a "?"
Both require exactly one of day-of-month and day-of-week to be ?, meaning "no specific value"; they refuse an expression that restricts both, or leaves both as *.
How do I check it will run when I expect?
The widget above lists the next runs in the time zone you choose, and flags any run that lands in a daylight-saving gap or a repeated hour. For a whole crontab, paste it into the crontab viewer.