What the expression does
0 0 1 * * runs at 00:00 on the first day of every month — January 1, February 1, March 1 and so on, twelve times per year.
The day-of-month field is fixed to 1, and the weekday field is *. If you set both day-of-month and weekday, cron combines them with OR, which is why some “monthly” expressions accidentally run weekly.
When this schedule is useful
- Generating monthly invoices or statements.
- Closing the previous month's accounting period.
- Monthly usage reports and quota resets.
- Archiving data into monthly partitions.
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:
- Monthly on the 15th:
0 0 15 * *— Mid-month statements or payouts. - Monthly at 02:00 on the 1st:
0 2 1 * *— A safer slot than midnight. - First business day (approx.):
0 9 1-3 * 1-5— Still OR semantics — verify before use. - Quarterly:
0 0 1 1,4,7,10 *— Every three months.
0 0 15 * * # Monthly on the 15th
0 2 1 * * # Monthly at 02:00 on the 1st
0 9 1-3 * 1-5 # First business day (approx.)
0 0 1 1,4,7,10 * # QuarterlyTimezone, 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.
The job runs at 00:00 on the 1st, which may be before the previous month's data has finished arriving. Schedule later in the day if upstream data lands at midnight.
“Last day of month” is not a valid Unix cron expression. 0 0 L * * is Quartz-only; in Unix, run on the 28th–31st and guard, or use a scheduler with end-of-month support.
A failed monthly job is expensive to recover because reruns can double-write invoices. Make the job idempotent and log the period it processed.
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.