Cron Atlas

Cron expression for once a year

0 0 1 1 *
minute0
hour0
day of month1st
monthJanuary
day of weekany weekday

At 00:00, on the 1st of the month, in January.

Next 10 runs

In Cron, worked out in your browser from the current time.

At a glance

Runs
1 in 2027
Gap between runs
365 days to 366 days
Expressible in
All six dialects
Clock changes
No effect in the zones checked

Open in the tester

In each dialect

Every expression here is generated by the tester’s own engine and checked run for run against the others, so “Exact” means the same clock times in the same zone. Each one links to the tester.

Cron
0 0 1 1 *
0 0 1 1 * /path/to/command
  • @yearly and @annually mean the same thing.
  • Runs in the machine’s time zone. cronie also reads a CRON_TZ= line above the entry; other crons may not.
Exact
EventBridge
0 0 1 1 ? *
aws events put-rule --name every-year --schedule-expression "cron(0 0 1 1 ? *)"
  • Wrap it in cron(…). Day of month is set (1), so day of week has to be ?. The final * is the required year field.
  • Scheduled rules always run in UTC. For local times, create it in EventBridge Scheduler with --schedule-expression-timezone.
Exact
Quartz
0 0 0 1 1 ?
CronScheduleBuilder.cronSchedule("0 0 0 1 1 ?")
  • The leading 0 is the seconds field, so it fires at the top of the minute. Day of month is set (1), so day of week has to be ?. The optional year is left off.
  • Uses the JVM’s default zone unless the trigger sets one with inTimeZone.
Exact
Kubernetes
0 0 1 1 *
schedule: "0 0 1 1 *"
  • @yearly and @annually mean the same thing.
  • Without timeZone under spec, these times are in the kube-controller-manager’s zone. A CRON_TZ= prefix in the schedule fails validation.
  • Kubernetes can occasionally create two Jobs for one scheduled time, or none, so make the job safe to repeat.
Exact
GitHub
0 0 1 1 *
- cron: '0 0 1 1 *'
  • GitHub warns that schedules can be delayed at high load, which includes the start of every hour, and that some queued jobs may be dropped. A different minute reduces the risk.
  • Times are UTC unless you add timezone: beside cron, with an IANA name.
  • In a public repository GitHub disables scheduled workflows after 60 days without repository activity. That is shorter than the gap between these runs, so in a quiet repository this can be switched off before it next fires.
Exact
Azure
0 0 0 1 1 *
[TimerTrigger("0 0 0 1 1 *")]
  • Six fields with seconds first, so the leading 0 fires at the top of the minute.
  • UTC unless the app sets WEBSITE_TIME_ZONE, which Linux Consumption and Flex Consumption plans do not support.
Exact

About this schedule

Midnight on 1 January, which is what @yearly and @annually expand to in cron and Kubernetes. A job that runs once a year is the one most likely to find its environment changed since the last run, so test it by hand with a temporary schedule.

Clock changes

None of these times falls in the hour that clocks skip or repeat in New York, London, Berlin, Helsinki or Sydney, so every dialect runs it normally all year there. Zones that change clocks at other hours can still differ.

Questions

What is the cron expression for once a year?
0 0 1 1 * in standard cron, Kubernetes and GitHub Actions. The other dialects differ: 0 0 1 1 ? * in EventBridge; 0 0 0 1 1 ? in Quartz; 0 0 0 1 1 * in Azure.
Is @yearly the same as 0 0 1 1 *?
Yes, in standard cron and in Kubernetes. GitHub Actions does not accept @ shortcuts, and EventBridge, Quartz and Azure have none, so write the fields out there.
Which time zone does it run in?
It depends on the scheduler. GitHub Actions, EventBridge rules and Azure use UTC unless you set a zone (timezone, EventBridge Scheduler’s --schedule-expression-timezone, WEBSITE_TIME_ZONE). Kubernetes uses .spec.timeZone or the controller manager’s zone, Quartz the JVM’s zone or inTimeZone, and cron the machine’s zone or CRON_TZ.

More schedules