0 0 1 1,4,7,10 *
Cron reads this as: at 00:00, on day-of-month 1, in month January, April, July and October.
Next 5 runs
Computed in your browser's local time zone. Cron itself evaluates against the server's zone, which on most cloud hosts is UTC — see time zones & DST if that distinction matters here.
- Calculating…
When to use this schedule
Midnight on the first of January, April, July and October — calendar quarters. Quarterly reporting, subscription renewals, periodic audits and compliance jobs.
What to watch out for
Calendar quarters and fiscal quarters are frequently not the same thing. If your financial year starts in February, you want 0 0 1 2,5,8,11 * instead. */3 in the month field gives the same calendar quarters but is harder to shift to a fiscal year, so an explicit list is usually the better choice. Four runs a year also means a broken job can stay broken for three months — test it by hand rather than waiting.
The crontab line
0 0 1 1,4,7,10 * /usr/local/bin/your-job.sh >> /var/log/your-job.log 2>&1Redirect the output somewhere you will actually read it — by default cron mails it, and on a host with no mail transport that means it is discarded. See the crontab guide for the surrounding syntax.
Related schedules
| Expression | Schedule |
|---|---|
0 0 1 */3 * | Same quarters, written as a step |
0 0 1 2,5,8,11 * | Fiscal year starting February |
0 0 1 1 * | Once a year |
Build your own
Need something this page does not cover? Compose it field by field in the visual builder, or paste an expression you already have into the explainer for a per-field breakdown. The examples library collects sixty schedules in one place, and the guides cover crontab syntax, time zones, troubleshooting and production practices.