Every Sunday at Midnight Cron Expression — 0 0 * * 0
Cron Expression
0 0 * * 0What it means
Runs every Sunday at midnight
A popular slot for full weekly database backups, running long integration test suites, or performing bulk data migrations during the quietest period of the week.
Next 8 Scheduled Runs (UTC)
- 1.Sun, 28 Jun 2026 00:00:00 GMT
- 2.Sun, 05 Jul 2026 00:00:00 GMT
- 3.Sun, 12 Jul 2026 00:00:00 GMT
- 4.Sun, 19 Jul 2026 00:00:00 GMT
- 5.Sun, 26 Jul 2026 00:00:00 GMT
- 6.Sun, 02 Aug 2026 00:00:00 GMT
- 7.Sun, 09 Aug 2026 00:00:00 GMT
- 8.Sun, 16 Aug 2026 00:00:00 GMT
Platform Snippets
GitHub Actions
- cron: '0 0 * * 0'
Kubernetes CronJob
schedule: "0 0 * * 0"
AWS EventBridge
cron(0 0 ? * SUN *)
AWS uses a 6-field format with year and requires either DOM or DOW to be ?.
systemd Timer
[Timer] OnCalendar=Sun *-*-* 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 * * 0 mean?
Runs every Sunday at midnight. A popular slot for full weekly database backups, running long integration test suites, or performing bulk data migrations during the quietest period of the week.
How do I use 0 0 * * 0 in GitHub Actions?
Add a schedule trigger under the "on" key in your workflow YAML: on: schedule: - cron: '0 0 * * 0'. This will run your workflow runs every sunday at midnight. Note that GitHub Actions uses UTC time.
Is the cron expression 0 0 * * 0 valid for Kubernetes CronJobs?
Yes. Set the schedule field in your CronJob spec to "0 0 * * 0". Kubernetes CronJobs use standard 5-field cron syntax and run in UTC by default unless you configure a timeZone field.