Curated cron expression
Daily at Noon in January Only: 0 12 * 1 *
0 12 * 1 * — month-restricted schedule for seasonal jobs.
Meaning at a glance
0 12 * 1 *
Run every day at 12:00 during January
Daily at noon in January; silent rest of year.
Next-run example: In July, no runs until next January.
How 0 12 * 1 * works
Month field 1 limits runs to January only.
Seasonal campaigns and tax-season jobs.
Preview next runs and platform conversions in CronWizard before deploying to production.
| Field | Value | Meaning |
|---|---|---|
| Minute | 0 | Configured as 0 |
| Hour | 12 | Configured as 12 |
| Day of month | * | Every value |
| Month | 1 | Configured as 1 |
| Day of week | * | Every value |
Good use cases
- Seasonal promos
- Tax season
- Winter-only features
Timezone and daylight-saving behavior
January boundary is timezone-dependent.
January rarely has DST changes in northern hemisphere.
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 12 * 1 * | Use directly in a normal five-field user crontab. |
| Kubernetes CronJob | Ready | 0 12 * 1 * | Use as spec.schedule; set spec.timeZone when local wall-clock behavior matters. |
| GitHub Actions | Ready | 0 12 * 1 * | Use under on.schedule; UTC is the default and an IANA timezone may be specified. |
| Vercel Cron Jobs | Plan / behavior limit | 0 12 * 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 12 ? 1 ? *) | Convert to AWS minute-first cron(...), add the required year, and use ? in one day field. |
| Spring @Scheduled | Convert | 0 0 12 * 1 * | Use Spring’s six fields by prepending seconds and set zone explicitly when needed. |
| systemd timer | Convert | 0 12 * 1 * | Use OnCalendar syntax and validate it with systemd-analyze calendar on the target host. |
Edge cases to check before deployment
- Forgotten jobs resume next January automatically.
Frequently asked questions
What does the cron expression 0 12 * 1 * mean?
0 12 * 1 * means “run every day at 12:00 during january.” Daily at noon in January; silent rest of year.
What are the next run times for 0 12 * 1 *?
In July, no runs until next January. Exact timestamps depend on the scheduler timezone and the current time.
What timezone does 0 12 * 1 * use?
January boundary is timezone-dependent.
Can I use 0 12 * 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.