Cron expression
First day of the quarter
0 0 1 1,4,7,10 *
Runs four times a year, at 00:00 on 1 January, 1 April, 1 July and 1 October.
Runs per month
≈ 1
Next run (UTC)
Fri 00:00
On CronEngine
Runs on the free plan
What each part means
| Minute | 0 | at minute 0 |
| Hour | 0 | at hour 0 |
| Day of month | 1 | on day 1 |
| Month | 1,4,7,10 | in January, April, July and October |
| Day of week | * | every day of the week |
Next runs
- 1 Friday 1 January 2027 00:00 UTC
- 2 Thursday 1 April 2027 00:00 UTC
- 3 Thursday 1 July 2027 00:00 UTC
- 4 Friday 1 October 2027 00:00 UTC
- 5 Saturday 1 January 2028 00:00 UTC
See these in your own timezone, or change the schedule →
Good to know
- The month field lists the first month of each quarter. The step form */3 gives the same result, because it counts from January: 1, 4, 7 and 10.
- A job this rare is easy to forget. Make sure someone hears about it if it fails, because the next try is three months away.
Typical uses: Quarterly reports, VAT and tax exports, archiving.
Copy and paste
0 0 1 1,4,7,10 * /path/to/script.sh
on:
schedule:
- cron: '0 0 1 1,4,7,10 *'
GitHub Actions reads this in UTC, and scheduled runs can start late when GitHub is busy. How to start it on time.
Schedule::command('your:command')->quarterly();
Variations
| 0 0 1 */3 * | The same schedule, with a step |
| 0 0 1 1 * | Once a year, on 1 January |
Questions
What is the cron expression for first day of the quarter?
0 0 1 1,4,7,10 *. Runs four times a year, at 00:00 on 1 January, 1 April, 1 July and 1 October.
Can GitHub Actions run first day of the quarter?
Yes, with cron: '0 0 1 1,4,7,10 *'. GitHub Actions reads this in UTC, and scheduled runs can start late when GitHub is busy.
More schedules: months
← All cron schedules · Cron cheat sheet · Cron expression generator