If you need a crontab entry that runs Monday through Friday and skips weekends, there's one small change to make. In the last field of your cron expression, replace the star (*) with 1-5. The expression 0 9 * * 1-5 runs your command at 9 AM every weekday. Saturdays and Sundays are ignored completely.
Below: how the weekday crontab expression works, how to limit it to business hours, the MON-FRI name syntax, what cron can and can't do about holidays, and how to check that jobs actually fire on the right days. For a broader look at cron syntax, see the complete cron jobs guide.
Quick answer:
0 9 * * 1-5The fifth field (day of week) accepts
1-5for Monday through Friday.MON-FRIworks the same way. Saturdays (6) and Sundays (0 or 7) are skipped.
How the weekday crontab expression works#
A cron expression has five fields, from left to right: minute, hour, day of month, month, and day of week. The day-of-week field is the last one. To limit your crontab schedule to working days, set it to 1-5. In cron, Monday is 1 and Friday is 5. The range 1-5 covers all five workdays.
0 9 * * 1-5 # 9:00 AM, Monday through Friday
0 0 * * 1-5 # Midnight, weekdays only
30 8 * * 1-5 # 8:30 AM on weekdays
With this setup, the job fires five times per week, roughly 260 times per year. Weekends are skipped entirely, and you can preview the next fire dates to confirm the schedule looks right before saving it.
1-5 vs MON-FRI: both work#
Instead of numbers, you can use three-letter day names. MON-FRI does exactly the same thing as 1-5:
0 9 * * MON-FRI # Same as 0 9 * * 1-5
Day names are case-insensitive on Linux, so mon-fri, Mon-Fri, and MON-FRI all work. On some older or minimal systems (Solaris, busybox crond), names aren't supported. Should your weekday crontab schedule do nothing and show no error, try the numeric version instead. Our expression validator can tell you whether your syntax is valid.
One gotcha worth knowing: some scheduling systems outside Linux, like Quartz (used in Java apps) and AWS EventBridge, number the days differently. In those systems, 1 means Sunday, not Monday. So a Monday-Friday range in Quartz would be 2-6. If you're copying a cron expression from a Linux server to one of these platforms, double-check which day is which.
Day-of-week field reference#
The day-of-week field (position 5) accepts values 0-7, where both 0 and 7 mean Sunday. Here's the full mapping:
| Number | Day | Short name |
|---|---|---|
| 0 | Sunday | SUN |
| 1 | Monday | MON |
| 2 | Tuesday | TUE |
| 3 | Wednesday | WED |
| 4 | Thursday | THU |
| 5 | Friday | FRI |
| 6 | Saturday | SAT |
| 7 | Sunday* | SUN |
*Both 0 and 7 represent Sunday in standard cron. Use whichever is clearer to your team.
Different scheduling systems number days differently, and this is where bugs hide:
| System | Sunday | Monday | Friday | Saturday | Weekday range |
|---|---|---|---|---|---|
| Linux cron | 0 (or 7) | 1 | 5 | 6 | 1-5 |
| Quartz / Spring | 1 | 2 | 6 | 7 | 2-6 or MON-FRI |
| AWS EventBridge | SUN | MON | FRI | SAT | MON-FRI |
| Go (robfig/cron) | 0 | 1 | 5 | 6 | 1-5 |
We've debugged this exact mismatch at least four times across different projects. Someone copies 1-5 from a Linux crontab into a Quartz config, and suddenly Sunday-through-Thursday runs instead of Monday-through-Friday. Nobody notices until the weekend job fires on a Sunday morning and wakes up the on-call engineer.
Cron Monday to Friday, 9 to 5 (business hours only)#
You can combine the day-of-week range with an hour range to exclude weekends and run jobs only during work hours. For example, every 15 minutes from 9 AM to 5 PM, Monday through Friday:
*/15 9-17 * * 1-5 # Every 15 min, 9 AM to 5 PM, Mon-Fri
That gives you 36 runs per workday and zero on weekends. More patterns like this:
*/30 9-17 * * 1-5 # Every 30 min during business hours
0 9-17 * * 1-5 # Once every hour, 9 AM to 5 PM
0 9,12,17 * * 1-5 # Three times a day: morning, lunch, end of day
A detail that catches people: the hour range 9-17 includes both 9:00 and 17:00. With */15, the last run of the day is at 17:45, not 17:00. If you want the last run at 4:45 PM, use 9-16 instead. Easy to miss, and it bit us once on a reporting script that fired an hour later than the team expected.
Picking specific weekdays#
You don't always need all five working days. Maybe a digest email goes out on Tuesday and Thursday, or a sync job runs Monday-Wednesday-Friday:
0 9 * * 2,4 # Tuesday and Thursday at 9 AM
0 9 * * 1,3,5 # Monday, Wednesday, Friday
0 9 * * 1-3 # Monday through Wednesday only
Numbers and ranges mix freely. 1,3-5 means Monday, Wednesday, Thursday, Friday (skipping Tuesday). Our cheat sheet shows how to mix ranges and lists.
Weekends only (the opposite)#
Sometimes you need the reverse: a heavy cleanup or database rebuild that should only run when the system is quiet and nobody is working.
0 3 * * 6,0 # 3 AM on Saturday and Sunday
0 3 * * SAT,SUN # Same thing with names
In standard cron, both 0 and 7 represent Sunday. So 6,0 and 6,7 both mean Saturday and Sunday.
What about holidays?#
Cron has no concept of holidays. The range 1-5 means Monday through Friday, every single week, no matter what. Christmas falls on a Friday? The job runs. National holiday on a Monday? Still fires. Cron follows the calendar, not your company's HR schedule.
When your job needs to skip holidays, you let cron run on weekdays as usual but add a check inside the script. Same idea as the "first business day" workaround from the monthly scheduling guide:
0 9 * * 1-5 /opt/scripts/check-holiday.sh && /opt/scripts/billing-run.sh
How this works: check-holiday.sh looks up today's date in a list of holidays. That list can be a simple text file, a database table, or an API call. If today is a holiday, the script exits with a non-zero code. The && between the two commands means the second script (billing) only runs when the first one succeeds. So on holidays, the billing script is skipped.
A minimal check-holiday.sh looks like this:
#!/bin/bash
TODAY=$(date +%Y-%m-%d)
grep -q "$TODAY" /etc/holidays.txt && exit 1
exit 0
Keep /etc/holidays.txt with one date per line (2026-12-25, 2027-01-01, and so on). We've seen teams run this setup for years with barely any maintenance. Not pretty, but reliable.
Putting it in your crontab#
To add a weekday schedule, open your crontab file:
crontab -e
Add the full path to your script. Cron doesn't load your shell profile, so short command names like python3 won't resolve — use absolute paths, and redirect output to a log file so you can trace failures later:
0 9 * * 1-5 /usr/bin/python3 /opt/scripts/weekday-report.py >> /var/log/weekday-report.log 2>&1
Appending >> saves output to the log file without overwriting it, and 2>&1 sends error messages to the same place. Without this, cron tries to email the output, which on most servers just means it vanishes. For more on capturing what your jobs write, see the cron job logging guide. To confirm your entry was saved:
crontab -l
For the same schedule across multiple servers, use drop-in files in /etc/cron.d/ instead. These work like a crontab but with one extra field: the username to run the command as:
# /etc/cron.d/weekday-report
0 9 * * 1-5 appuser /usr/bin/python3 /opt/scripts/weekday-report.py >> /var/log/weekday-report.log 2>&1
Weekday cron on different platforms#
The expression 0 9 * * 1-5 is standard crontab syntax, but every platform wraps it differently. Here's how to schedule a weekday job on each one:
Kubernetes CronJob
apiVersion: batch/v1
kind: CronJob
metadata:
name: weekday-report
spec:
schedule: "0 9 * * 1-5"
timeZone: "America/New_York"
jobTemplate:
spec:
template:
spec:
containers:
- name: report
image: myapp:latest
command: ["python", "report.py"]
restartPolicy: OnFailure
Starting with Kubernetes 1.27, the timeZone field (beta, enabled by default) lets you schedule in local time instead of UTC. Without it, 0 9 * * 1-5 means 9 AM UTC, which might not be 9 AM where your team works. Our timezone converter helps figure out the right hour. See the Kubernetes cron guide for more details on job concurrency and backoff limits.
GitHub Actions
on:
schedule:
- cron: '0 14 * * 1-5' # 9 AM ET (UTC-5)
GitHub Actions cron always runs in UTC. No timezone override exists. If you need 9 AM Eastern, schedule at 14:00 UTC (during EST) and accept the one-hour drift during daylight saving time. MON-FRI names work in GitHub Actions since it uses standard POSIX cron parsing.
AWS EventBridge
cron(0 9 ? * MON-FRI *)
AWS uses six fields (the last one is year) and requires ? in either day-of-month or day-of-week when the other is specified. That ? means "no specific value." Classic EventBridge Rules run in UTC only; the newer EventBridge Scheduler supports ScheduleExpressionTimezone.
systemd timer
[Timer]
OnCalendar=Mon..Fri *-*-* 09:00:00
Persistent=true
systemd uses its own calendar syntax, not cron expressions. Mon..Fri is the weekday range. Setting Persistent=true means if the system was off during a scheduled time, it'll run the job on the next boot. We switched two of our internal jobs from cron to systemd timers last year, and the Persistent flag alone justified the move. Since systemd 247, you can append a timezone: OnCalendar=Mon..Fri *-*-* 09:00:00 America/New_York.
Docker (cron inside container)
RUN echo "0 9 * * 1-5 /app/script.sh >> /proc/1/fd/1 2>&1" | crontab -
Redirecting to /proc/1/fd/1 sends cron output to Docker's stdout, so docker logs picks it up. Set TZ=America/New_York as an environment variable if you need local time instead of UTC. See the Docker cron guide for multi-stage build examples.
Laravel
$schedule->command('report:daily')
->weekdays()
->at('09:00');
Laravel's weekdays() method maps to 1-5 internally. You can chain it with timezone('America/New_York') if the server runs in UTC. More in the Laravel task scheduling guide.
Python (APScheduler)
from apscheduler.schedulers.blocking import BlockingScheduler
sched = BlockingScheduler()
sched.add_job(weekday_report, 'cron', day_of_week='mon-fri', hour=9)
sched.start()
APScheduler uses the same day names as POSIX cron. For standard library alternatives, see the Python cron jobs guide.
Mistakes that trip people up#
Mixing day-of-month with day-of-week. Say you write 0 9 1-15 * 1-5, thinking it means "weekdays in the first half of the month." It doesn't. When you put specific values in both the day-of-month and day-of-week fields, cron treats them as OR, not AND. The job runs on days 1-15 plus every weekday, which is almost every day — far more often than you intended, and the extra runs can pile up fast enough to overload a database or blow through API rate limits before anyone notices. Check the day-of-month inside the script instead. Our first-day-of-month guide explains this trap.
Sunday = 0 or 1? In standard Linux cron, Sunday is 0 (or 7). Quartz (a Java scheduling library used by many apps) starts at 1 for Sunday. Writing 1-5 in Quartz gives you Sunday through Thursday. Not what you wanted. Always check which numbering your system uses.
Timezone mix-ups. A "weekday 9 AM" job on a UTC server fires at 4 AM Eastern or 2 AM Pacific on the same day. Worse: "Friday 11 PM UTC" is already Saturday morning in Tokyo, so a job meant for weekdays hits a weekend for your Tokyo team. That one wasted a solid hour of debugging for us before we figured out the offset. Use the timezone converter to find the right UTC hour.
Silent failures. You set up a weekday crontab entry, nothing happens, and there's no error message. Usually it's a PATH issue, a permission problem, or a missing shebang line. Our cron job not running troubleshooting guide walks through every common cause.
Checking that it actually fires#
Weekday schedules can be hard to test. Set one up on a Friday evening and the first run won't happen until Monday. Three days of silence before you know whether it works.
grep CRON /var/log/syslog | grep "weekday-report" | tail -10
That command filters syslog for cron invocations of your script and shows the last ten, which tells you whether cron even attempted the run — though it says nothing about whether the script itself succeeded, exited cleanly, or produced the output your team actually needed. Nobody checks logs manually every Monday morning anyway.
Better approach: add a heartbeat ping to the end of your cron line. After the script finishes, it sends a quick HTTP request to a monitoring URL:
0 9 * * 1-5 /opt/scripts/weekday-report.py && curl -fsS https://watchcron.com/ping/your-token
If the ping doesn't arrive on a weekday when it should, you get an alert right away. For weekday-only jobs, set the monitor to expect pings only Monday through Friday so it doesn't alert on weekends. WatchCron supports 10+ alert channels including Slack, Telegram, and email.
Weekday crontab examples#
| Schedule | Expression | Runs/week |
|---|---|---|
| Every weekday at 9 AM | 0 9 * * 1-5 | 5 |
| Every weekday at midnight | 0 0 * * 1-5 | 5 |
| 8 AM and 5 PM on weekdays | 0 8,17 * * 1-5 | 10 |
| Morning, lunch, end of day | 0 9,12,17 * * 1-5 | 15 |
| Every hour, business hours | 0 9-17 * * 1-5 | 45 |
| Every 15 min, business hours | */15 9-17 * * 1-5 | ~180 |
| Every 30 min, business hours | */30 9-17 * * 1-5 | ~90 |
| Every 2 hours on weekdays | 0 */2 * * 1-5 | 60 |
| Every 4 hours on weekdays | 0 */4 * * 1-5 | 30 |
| 6 AM weekdays (early morning) | 0 6 * * 1-5 | 5 |
| 11:30 PM weekdays (cleanup) | 30 23 * * 1-5 | 5 |
| Every Monday at 9 AM | 0 9 * * 1 | 1 |
| Every Friday at 9 AM | 0 9 * * 5 | 1 |
| Mon/Wed/Fri at 9 AM | 0 9 * * 1,3,5 | 3 |
| Tue/Thu at 9 AM | 0 9 * * 2,4 | 2 |
| Weekdays using names | 0 9 * * MON-FRI | 5 |
| Weekends only at 3 AM | 0 3 * * 0,6 | 2 |
Use the cron calculator to verify exact run counts — month boundaries and leap years shift the annual totals slightly. More patterns in the cron expression examples library.
When you can't edit crontab#
On managed hosting, in containers without a cron daemon, or in serverless setups, you can't open a crontab file. An external scheduler solves this: you give it a URL and a schedule like 0 9 * * 1-5, and it calls your endpoint on weekdays from its own servers.
In Kubernetes, you can define a CronJob resource with the same expression. The schedule field accepts standard cron syntax, so "0 9 * * 1-5" works as-is. The cluster handles the scheduling; you just need to make sure the pod's timezone matches what you expect.
If the scheduler also checks whether your endpoint responded and retries on failure, you get both scheduling and monitoring in one setup. WatchCron's Cloud Cron works this way, with three free scheduled jobs on the free plan.
One Cloud Cron job and 20 monitoring checks on the free plan. No credit card.
Frequently asked#
0 9 * * 1-5 runs at 9 AM every weekday.1-5 and MON-FRI both mean Monday through Friday. Numeric form works everywhere; names may not work on minimal systems like busybox.*/15 9-17 * * 1-5 runs every 15 minutes from 9 AM to 5 PM, Monday through Friday.0 9 * * 2,4 for Tuesday and Thursday, 0 9 * * 1,3,5 for Monday/Wednesday/Friday. Numbers and ranges mix freely.0 9 * * 1-5. Add spec.timeZone to run in local time instead of UTC. The timeZone field requires Kubernetes 1.25+.MON-FRI works. But the schedule always runs in UTC — there is no timezone override.0 9 * * 1,2,4,5. This runs Monday, Tuesday, Thursday, and Friday.1-5 in the fifth field restricts execution to weekdays only.0 0 * * 1-5. The first two zeros set minute and hour to 0 (midnight), and 1-5 limits it to Monday through Friday.0 9 * * 1-5, where 1-5 represents Monday through Friday. Replace 0 9 with your desired minute and hour.