All Cron Schedules
Cron Weekdays at 9 AM
Run a cron job Monday through Friday at 9:00 AM:
0 9 * * 1-5
Understanding the Expression
The cron expression 0 9 * * 1-5 breaks down as follows:
| Field | Value | Meaning |
|---|---|---|
| Minute | 0 | At minute 0 |
| Hour | 9 | At 9:00 |
| Day of month | * | Every day of the month |
| Month | * | Every month |
| Day of week | 1-5 | Monday through Friday |
Example Usage
Basic crontab entry
0 9 * * 1-5 /path/to/your/script.sh
With output logging
0 9 * * 1-5 /path/to/script.sh >> /var/log/script.log 2>&1
With monitoring
0 9 * * 1-5 /path/to/script.sh && curl -fsS https://cronsignal.io/ping/YOUR_CHECK_ID
Common Use Cases for Weekdays at 9 AM
- Business hour jobs: Run tasks during working hours only
- Off-peak processing: Heavy tasks during low-traffic periods
- Scheduled notifications: Send alerts during appropriate hours
- Workday automation: Automate business processes on weekdays
Platform Equivalents
The same schedule expressed across common platforms and schedulers:
| Platform | Syntax |
|---|---|
| Linux crontab | 0 0 * * 1-5 |
| GitHub Actions | - cron: '0 0 * * 1-5' |
| systemd timer | OnCalendar=Mon..Fri *-*-* 00:00:00 |
| Kubernetes CronJob | schedule: "0 0 * * 1-5" |
| AWS EventBridge | cron(0 0 ? * MON-FRI *) |
Timezone Considerations
Midnight UTC on weekdays equals Sunday 7-8 PM in US timezones — still the weekend locally. For true weekday-morning runs, adjust the UTC hour for your server timezone.
Common Mistakes
- Day numbering:
1-5means Monday through Friday. Day 0 and day 7 both equal Sunday. - Day-of-month + day-of-week OR logic: If both fields are non-
*, the job runs when either is true — not when both are true. - AWS EventBridge: Uses day names and requires
?for day-of-month:cron(0 0 ? * MON-FRI *).
Monitor this schedule
Get alerted when your cron job doesn't run.
Sign up with Google
or
3 checks free. No credit card required.