Yearly on January 1st Cron Expression — 0 0 1 1 *
Cron Expression
0 0 1 1 *What it means
Runs once a year on January 1st at midnight
Suitable for annual data archiving, resetting yearly counters or quotas, and generating year-in-review reports automatically at the start of each new year.
Next 8 Scheduled Runs (UTC)
- 1.Fri, 01 Jan 2027 00:00:00 GMT
- 2.Sat, 01 Jan 2028 00:00:00 GMT
- 3.Mon, 01 Jan 2029 00:00:00 GMT
- 4.Tue, 01 Jan 2030 00:00:00 GMT
- 5.Wed, 01 Jan 2031 00:00:00 GMT
- 6.Thu, 01 Jan 2032 00:00:00 GMT
- 7.Sat, 01 Jan 2033 00:00:00 GMT
- 8.Sun, 01 Jan 2034 00:00:00 GMT
Platform Snippets
GitHub Actions
- cron: '0 0 1 1 *'
Kubernetes CronJob
schedule: "0 0 1 1 *"
AWS EventBridge
cron(0 0 1 1 ? *)
AWS uses a 6-field format with year and requires either DOM or DOW to be ?.
systemd Timer
[Timer] OnCalendar=*-*-1 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 1 * mean?
Runs once a year on January 1st at midnight. Suitable for annual data archiving, resetting yearly counters or quotas, and generating year-in-review reports automatically at the start of each new year.
How do I use 0 0 1 1 * in GitHub Actions?
Add a schedule trigger under the "on" key in your workflow YAML: on: schedule: - cron: '0 0 1 1 *'. This will run your workflow runs once a year on january 1st at midnight. Note that GitHub Actions uses UTC time.
Is the cron expression 0 0 1 1 * valid for Kubernetes CronJobs?
Yes. Set the schedule field in your CronJob spec to "0 0 1 1 *". Kubernetes CronJobs use standard 5-field cron syntax and run in UTC by default unless you configure a timeZone field.