Curated cron expression
Quarterly on 1st at Midnight: 0 0 1 1,4,7,10 *
0 0 1 1,4,7,10 * — quarterly schedule on first day of quarter months.
Meaning at a glance
0 0 1 1,4,7,10 *
Run on Jan, Apr, Jul, Oct 1st at 00:00
Four times per year at midnight on quarter start.
Next-run example: After April 1 run, next is July 1 00:00.
How 0 0 1 1,4,7,10 * works
Month list 1,4,7,10 selects quarter starts.
Used for quarterly billing and compliance reports.
Preview next runs and platform conversions in CronWizard before deploying to production.
| Field | Value | Meaning |
|---|---|---|
| Minute | 0 | Configured as 0 |
| Hour | 0 | Configured as 0 |
| Day of month | 1 | Configured as 1 |
| Month | 1,4,7,10 | Configured as 1,4,7,10 |
| Day of week | * | Every value |
Good use cases
- Quarterly SEC filings
- License true-ups
- Quarterly analytics
Timezone and daylight-saving behavior
Quarter start midnight is timezone-sensitive.
Jan 1 and DST rarely conflict; still use UTC for audit logs.
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 0 1 1,4,7,10 * | Use directly in a normal five-field user crontab. |
| Kubernetes CronJob | Ready | 0 0 1 1,4,7,10 * | Use as spec.schedule; set spec.timeZone when local wall-clock behavior matters. |
| GitHub Actions | Ready | 0 0 1 1,4,7,10 * | Use under on.schedule; UTC is the default and an IANA timezone may be specified. |
| Vercel Cron Jobs | Plan / behavior limit | 0 0 1 1,4,7,10 * | The expression is valid, but Vercel always uses UTC and Hobby schedules run at most once per day. |
| AWS EventBridge Scheduler | Convert | cron(0 0 1 1,4,7,10 ? *) | Convert to AWS minute-first cron(...), add the required year, and use ? in one day field. |
| Spring @Scheduled | Convert | 0 0 0 1 1,4,7,10 * | Use Spring’s six fields by prepending seconds and set zone explicitly when needed. |
| systemd timer | Convert | 0 0 1 1,4,7,10 * | Use OnCalendar syntax and validate it with systemd-analyze calendar on the target host. |
Edge cases to check before deployment
- Verify month list matches fiscal calendar.
Frequently asked questions
What does the cron expression 0 0 1 1,4,7,10 * mean?
0 0 1 1,4,7,10 * means “run on jan, apr, jul, oct 1st at 00:00.” Four times per year at midnight on quarter start.
What are the next run times for 0 0 1 1,4,7,10 *?
After April 1 run, next is July 1 00:00. Exact timestamps depend on the scheduler timezone and the current time.
What timezone does 0 0 1 1,4,7,10 * use?
Quarter start midnight is timezone-sensitive.
Can I use 0 0 1 1,4,7,10 * 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.