Curated cron expression
Yearly on January 1 at Midnight: 0 0 1 1 *
0 0 1 1 * — annual New Year job for resets and archival.
Meaning at a glance
0 0 1 1 *
Run once per year on January 1 at 00:00
Once per year at Jan 1 00:00.
Next-run example: After Jan 1 2026, next is Jan 1 2027 00:00.
How 0 0 1 1 * works
Month 1 and day 1 select January 1 only.
Annual jobs for retention policies and year rollover.
Preview next runs and platform conversions in CronWizard before deploying to production.
| Field | Value | Meaning |
|---|---|---|
| Minute | 0 | Configured as 0 |
| Hour | 0 | Configured as 0 |
| Day of month | 1 | Configured as 1 |
| Month | 1 | Configured as 1 |
| Day of week | * | Every value |
Good use cases
- Annual archival
- Year rollover
- New year campaigns
Timezone and daylight-saving behavior
New Year instant differs globally — pick one timezone.
Most zones stable at Jan 1 midnight.
The expression does not contain a timezone. The scheduler supplies that context. Use the next-run preview above in the same IANA timezone as production, then confirm the target platform's own timezone rules.
Platform compatibility and converted expressions
The source expression is five-field Unix cron. Use the exact equivalent below rather than adding or removing fields by sight.
| Platform | Status | Expression | What to know |
|---|---|---|---|
| Unix crontab | Ready | 0 0 1 1 * | Use directly in a normal five-field user crontab. |
| Kubernetes CronJob | Ready | 0 0 1 1 * | Use as spec.schedule; set spec.timeZone when local wall-clock behavior matters. |
| GitHub Actions | Ready | 0 0 1 1 * | Use under on.schedule; UTC is the default and an IANA timezone may be specified. |
| Vercel Cron Jobs | Plan / behavior limit | 0 0 1 1 * | The expression is valid, but Vercel always uses UTC and Hobby schedules run at most once per day. |
| AWS EventBridge Scheduler | Convert | cron(0 0 1 1 ? *) | Convert to AWS minute-first cron(...), add the required year, and use ? in one day field. |
| Spring @Scheduled | Convert | 0 0 0 1 1 * | Use Spring’s six fields by prepending seconds and set zone explicitly when needed. |
| systemd timer | Convert | 0 0 1 1 * | Use OnCalendar syntax and validate it with systemd-analyze calendar on the target host. |
Edge cases to check before deployment
- UTC Jan 1 ≠ local New Year everywhere.
Frequently asked questions
What does the cron expression 0 0 1 1 * mean?
0 0 1 1 * means “run once per year on january 1 at 00:00.” Once per year at Jan 1 00:00.
What are the next run times for 0 0 1 1 *?
After Jan 1 2026, next is Jan 1 2027 00:00. Exact timestamps depend on the scheduler timezone and the current time.
What timezone does 0 0 1 1 * use?
New Year instant differs globally — pick one timezone.
Can I use 0 0 1 1 * on every scheduling platform?
No. It is a five-field Unix expression. Some platforms accept it directly, while AWS EventBridge Scheduler, Spring, and systemd require the converted form shown in the compatibility table.