Curated cron expression
Daily at 9 AM in December: 0 9 * 12 *
0 9 * 12 * — December-only daily schedule for holiday campaigns.
Meaning at a glance
0 9 * 12 *
Run every day at 09:00 in December
Daily 09:00 throughout December.
Next-run example: On Dec 15, next run is Dec 16 09:00.
How 0 9 * 12 * works
Month 12 restricts to December.
Holiday retail and year-end operations.
Preview next runs and platform conversions in CronWizard before deploying to production.
| Field | Value | Meaning |
|---|---|---|
| Minute | 0 | Configured as 0 |
| Hour | 9 | Configured as 9 |
| Day of month | * | Every value |
| Month | 12 | Configured as 12 |
| Day of week | * | Every value |
Good use cases
- Holiday marketing
- Year-end inventory
- Seasonal support staffing
Timezone and daylight-saving behavior
Global holidays differ — month filter alone is not enough for business holidays.
December DST minimal in most regions.
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 9 * 12 * | Use directly in a normal five-field user crontab. |
| Kubernetes CronJob | Ready | 0 9 * 12 * | Use as spec.schedule; set spec.timeZone when local wall-clock behavior matters. |
| GitHub Actions | Ready | 0 9 * 12 * | Use under on.schedule; UTC is the default and an IANA timezone may be specified. |
| Vercel Cron Jobs | Plan / behavior limit | 0 9 * 12 * | The expression is valid, but Vercel always uses UTC and Hobby schedules run at most once per day. |
| AWS EventBridge Scheduler | Convert | cron(0 9 ? 12 ? *) | Convert to AWS minute-first cron(...), add the required year, and use ? in one day field. |
| Spring @Scheduled | Convert | 0 0 9 * 12 * | Use Spring’s six fields by prepending seconds and set zone explicitly when needed. |
| systemd timer | Convert | 0 9 * 12 * | Use OnCalendar syntax and validate it with systemd-analyze calendar on the target host. |
Edge cases to check before deployment
- Combine with app logic for Christmas if needed.
Frequently asked questions
What does the cron expression 0 9 * 12 * mean?
0 9 * 12 * means “run every day at 09:00 in december.” Daily 09:00 throughout December.
What are the next run times for 0 9 * 12 *?
On Dec 15, next run is Dec 16 09:00. Exact timestamps depend on the scheduler timezone and the current time.
What timezone does 0 9 * 12 * use?
Global holidays differ — month filter alone is not enough for business holidays.
Can I use 0 9 * 12 * 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.