Home โบ Cron errors โบ GitHub Actions
GitHub Actions: day-of-week must be 0-6
Why this happens
Some cron systems accept 7 for Sunday. GitHub Actions uses POSIX cron with 0-6, so 7 is out of range.
Wrong and right
0 0 * * 7Our parser says: dow value 7 is out of range (0-6)
0 0 * * 0At 00:00 UTC, on Sun. First runs after 1 Jan 2027 (UTC): Sun 03 Jan, 00:00, Sun 10 Jan, 00:00, Sun 17 Jan, 00:00, Sun 24 Jan, 00:00, Sun 31 Jan, 00:00
How to fix it
- Use 0 for Sunday.
- Or write SUN.
- Check the Actions tab for a schedule parse error after pushing.
The GitHub Actions format at a glance
Fields in order: minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-6, 0 = Sunday).
GitHub Actions schedules are always UTC. Convert your local time to UTC before writing the expression.
The fixed schedule in other systems
If you are moving this schedule to another scheduler, these are the equivalents of 0 0 * * 0:
| System | Expression |
|---|---|
| Quartz | 0 0 0 ? * 1 |
| Spring | 0 0 0 * * 0 |
| Crontab | 0 0 * * 0 |
| Kubernetes | 0 0 * * 0 |
| AWS EventBridge | 0 0 ? * 1 * |
| Jenkins | 0 0 * * 0 |
| node-cron | 0 0 * * 0 |
| Apache Airflow | 0 0 * * 0 |
| Azure Functions | 0 0 0 * * 0 |
| Google Cloud Scheduler | 0 0 * * 0 |
Try it yourself
The tester below starts with the fixed expression. Change it and watch the schedule update.
Your week at a glance
Upcoming runs
| # | Local | UTC | From now |
|---|
Copy-ready code
Frequently asked questions
Why did my workflow vanish from the schedule?
An invalid cron makes GitHub ignore the schedule trigger. Check the workflow file for errors.
More GitHub Actions fixes
See the full GitHub Actions cron builder or convert between formats.