What the expression does

0 9 * * 1-5 runs at 09:00 Monday through Friday. The weekday range 1-5 covers Monday, Tuesday, Wednesday, Thursday and Friday.

A range in the weekday field is inclusive. 1-5 excludes Saturday (6) and Sunday (0/7). This is the canonical “weekdays only” expression in Unix cron.

When this schedule is useful

  • Daily digest or standup reminder at 09:00 on workdays.
  • Business-hour API polling between 9 and 5.
  • Report generation before the office opens.
  • Reminder emails that should not arrive on weekends.

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 — One run per workday morning.
  • Every 30 min, 9–17: */30 9-17 * * 1-5 — Business-hour polling.
  • Weekdays at 18:00: 0 18 * * 1-5 — End-of-day summary.
  • Monday, Wednesday, Friday: 0 9 * * 1,3,5 — Three runs per week.
cron
0 9 * * 1-5        # Weekdays at 09:00
*/30 9-17 * * 1-5  # Every 30 min, 9–17
0 18 * * 1-5       # Weekdays at 18:00
0 9 * * 1,3,5      # Monday, Wednesday, Friday

Timezone, 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.

Holidays are not weekends. A Monday public holiday still triggers the job unless you add a calendar check.

“Business hours” is usually more than one line: */30 9-17 * * 1-5 runs every 30 minutes during a nine-hour window, which is 18 runs per day, not one.

If the server is UTC and staff are in UTC+8, 09:00 UTC is 17:00 local — the digest arrives at the end of the day.

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.