What the expression does
0 9 * * 1 runs at 09:00 every Monday. Minute 0, hour 9, weekday 1 (Monday).
Day-of-week numbering starts at 0 for Sunday in Unix cron, so Monday is 1, Tuesday 2 and so on. This is the single most common mapping mistake when migrating from Quartz, where 1 means Sunday.
When this schedule is useful
- Weekly kickoff digest or team summary email.
- Refreshing dashboards before the Monday standup.
- Assigning weekly on-call rotations or reminders.
- Pulling weekend data into reporting tables.
Nearby expressions worth knowing
Small changes to one field produce very different schedules. These variants are the ones people usually want when they search for this cadence:
- Weekdays at 09:00:
0 9 * * 1-5— Monday through Friday. - Monday, Wednesday, Friday:
0 9 * * 1,3,5— Three digests per week. - Monday at 08:00 UTC:
0 8 * * 1— For teams whose local 09:00 is UTC+1. - First Monday of the month:
0 9 1-7 * 1— Do not use this — OR semantics makes it fire on the 1st–7th AND Mondays.
0 9 * * 1-5 # Weekdays at 09:00
0 9 * * 1,3,5 # Monday, Wednesday, Friday
0 8 * * 1 # Monday at 08:00 UTC
0 9 1-7 * 1 # First Monday of the monthTimezone, load and edge cases
Cron evaluates this expression in the timezone of the daemon, not the timezone of the person who wrote it. If the server runs UTC, a schedule that looks like a morning job can fire in the middle of the local night. Select the server timezone in the next-run preview and compare the wall-clock time before deploying.
If the host runs UTC, 09:00 UTC may be 17:00 in Shanghai or 01:00 in San Francisco. Convert the intended local time to UTC, or configure CRON_TZ.
Public holidays are not part of cron. A Monday holiday still runs the job; guard it with a holiday calendar check if that matters.
0 9 * * 1 is not “the first Monday of the month”. Cron cannot express nth-weekday without Quartz's # syntax.
If the schedule runs more often than you expect, check whether day-of-month and day-of-week are both restricted — Vixie cron treats that combination as OR, not AND.
Verify it before shipping
- Run the expression through the explainer and read the English sentence once.
- Check the next five run times in the server's timezone, not your laptop's.
- Execute the command manually with the same user and environment cron will use.
- Redirect stdout and stderr to a log file, and include a timestamp in each line.