Every Weekday at Midnight Cron Expression — 0 0 * * 1-5
Cron Expression
0 0 * * 1-5What it means
Runs Monday–Friday at midnight
Used for nightly data refreshes or ETL jobs that only need to run on business days, avoiding weekend processing costs.
Next 8 Scheduled Runs (UTC)
- 1.Tue, 14 Jul 2026 00:00:00 GMT
- 2.Wed, 15 Jul 2026 00:00:00 GMT
- 3.Thu, 16 Jul 2026 00:00:00 GMT
- 4.Fri, 17 Jul 2026 00:00:00 GMT
- 5.Mon, 20 Jul 2026 00:00:00 GMT
- 6.Tue, 21 Jul 2026 00:00:00 GMT
- 7.Wed, 22 Jul 2026 00:00:00 GMT
- 8.Thu, 23 Jul 2026 00:00:00 GMT
Platform Snippets
GitHub Actions
- cron: '0 0 * * 1-5'
Kubernetes CronJob
schedule: "0 0 * * 1-5"
AWS EventBridge
cron(0 0 ? * MON-FRI *)
AWS uses a 6-field format with year and requires either DOM or DOW to be ?.
systemd Timer
[Timer] OnCalendar=1-5 *-*-* 00:00:00 Persistent=true
Want to decode a different expression or test your own?
Test this expression interactively →FAQ
What does the cron expression 0 0 * * 1-5 mean?
Runs Monday–Friday at midnight. Used for nightly data refreshes or ETL jobs that only need to run on business days, avoiding weekend processing costs.
How do I use 0 0 * * 1-5 in GitHub Actions?
Add a schedule trigger under the "on" key in your workflow YAML: on: schedule: - cron: '0 0 * * 1-5'. This will run your workflow runs monday–friday at midnight. Note that GitHub Actions uses UTC time.
Is the cron expression 0 0 * * 1-5 valid for Kubernetes CronJobs?
Yes. Set the schedule field in your CronJob spec to "0 0 * * 1-5". Kubernetes CronJobs use standard 5-field cron syntax and run in UTC by default unless you configure a timeZone field.