Cron expression tester › 0 0 1 1 *
What does 0 0 1 1 * mean?
Once a year (Jan 1 at midnight). Runs at 00:00 on January 1st. Equivalent to the non-standard @yearly / @annually.
Annual resets: yearly report kickoffs, license renewals, and counters that roll over on New Year's Day.
Next scheduled runs
Calculating…
Field-by-field breakdown
| Value | Field | Meaning |
|---|---|---|
0 | Minute (0–59) | exactly 0 |
0 | Hour (0–23) | exactly 0 |
1 | Day of month (1–31) | exactly 1 |
1 | Month (1–12) | exactly 1 |
* | Day of week (0–6, Sun=0) | every value |
Standard 5-field Vixie/POSIX cron: minute hour day-of-month month day-of-week. Cron uses the server's local timezone unless configured otherwise. Non-standard extensions (@daily, L, W, #, seconds) aren't evaluated here.
Open this schedule in the interactive tester →
Will you know if a once a year (jan 1 at midnight) run is skipped?
Knowing when 0 0 1 1 * should fire is only half of it. The failure that hurts is the silent one — the box was asleep, the trigger broke, the token expired, and nobody noticed. Cronpulse is a free dead-man's-switch: your job pings a URL each time it runs on this schedule, and if a ping goes missing, we alert you by email, Discord, Slack, or webhook.
Monitor a once a year (jan 1 at midnight) job — free → No signup needed to start.
Related cron schedules
| Schedule | Meaning |
|---|---|
0 0 * * 5 | Every Friday at midnight |
0 8 * * 1 | Every Monday at 8:00 AM |
15 10 * * * | Every day at 10:15 AM |
* * * * * | Every minute |
*/5 * * * * | Every 5 minutes |
All common cron expressions → · Monitor scheduled jobs → · Monitor an AI agent →