Every year on January 1st at midnight
0 0 1 1 *The cron expression 0 0 1 1 * means: at 12:00 AM on the 1st in Jan.
Field breakdown
A standard cron expression has five fields. Here is how this one is parsed, field by field.
| Field | Value | Allowed range |
|---|---|---|
| Minute | 0 | 0-59 |
| Hour | 0 | 0-23 |
| Day of Month | 1 | 1-31 |
| Month | 1 | 1-12 |
| Day of Week | * | 0-6 (Sun-Sat) |
Things to watch for
This fires rarely — roughly once every 12 months. Double-check this is the intended cadence.
Next run times
The upcoming runs below are calculated in your browser, so they are always current. Times are shown in UTC and in your local timezone.
| UTC | Your time (UTC) |
|---|---|
| Fri, Jan 1, 2027, 12:00 AM | Fri, Jan 1, 2027, 12:00 AM |
| Sat, Jan 1, 2028, 12:00 AM | Sat, Jan 1, 2028, 12:00 AM |
| Mon, Jan 1, 2029, 12:00 AM | Mon, Jan 1, 2029, 12:00 AM |
| Tue, Jan 1, 2030, 12:00 AM | Tue, Jan 1, 2030, 12:00 AM |
| Wed, Jan 1, 2031, 12:00 AM | Wed, Jan 1, 2031, 12:00 AM |
Open this expression in the validator for a calendar view and other timezones.
Use this schedule on your platform
The same schedule, written for common platforms. Select a platform for a full guide and a ready-to-use configuration.
| Platform | Schedule |
|---|---|
| GitHub Actions | 0 0 1 1 * |
| Vercel Cron | 0 0 1 1 * |
| Kubernetes CronJob | 0 0 1 1 * |
| AWS EventBridge | cron(0 0 1 1 ? *) |
| node-cron | 0 0 1 1 * |
See all cron converters for the full list of platforms.