What the expression does
0 0 1 1,4,7,10 * runs at midnight on January 1, April 1, July 1 and October 1 — four times a year, at the start of each calendar quarter.
The month field contains a list of four values. A list is evaluated as a union, so any of those months matches. The day-of-month is fixed to 1 and the weekday is unrestricted.
When this schedule is useful
- Quarterly financial reports and board decks.
- Reconciling tax or compliance filings.
- Purging data older than the retention window once per quarter.
- Recalculating long-horizon forecasts or snapshots.
Nearby expressions worth knowing
Small changes to one field produce very different schedules. These variants are the ones people usually want when they search for this cadence:
- Quarterly at 02:00:
0 2 1 1,4,7,10 *— After upstream data settles. - Semi-annual:
0 0 1 1,7 *— January and July. - Every 3 months from April:
0 0 1 4,7,10,1 *— Same set, different order; fiscal year starting April. - Monthly:
0 0 1 * *— Twelve runs instead of four.
0 2 1 1,4,7,10 * # Quarterly at 02:00
0 0 1 1,7 * # Semi-annual
0 0 1 4,7,10,1 * # Every 3 months from April
0 0 1 * * # MonthlyTimezone, load and edge cases
Cron evaluates this expression in the timezone of the daemon, not the timezone of the person who wrote it. If the server runs UTC, a schedule that looks like a morning job can fire in the middle of the local night. Select the server timezone in the next-run preview and compare the wall-clock time before deploying.
Calendar quarters are not fiscal quarters. If your company's fiscal year starts in February, the four dates are different; do not copy the expression without checking.
Quarter-end data often arrives late. A run at 00:00 on the 1st may process an incomplete prior quarter; schedule a few hours later or add a readiness check.
Sparse jobs need explicit alerting. If a quarterly run fails, waiting for the next natural run means six months of missing data.
If the schedule runs more often than you expect, check whether day-of-month and day-of-week are both restricted — Vixie cron treats that combination as OR, not AND.
Verify it before shipping
- Run the expression through the explainer and read the English sentence once.
- Check the next five run times in the server's timezone, not your laptop's.
- Execute the command manually with the same user and environment cron will use.
- Redirect stdout and stderr to a log file, and include a timestamp in each line.