ClockOrbit

Monthly

0 0 1 1,4,7,10 *

Run on the 1st of January, April, July, and October at midnight.

This preview is live: the table below shows the actual next run times for 0 0 1 1,4,7,10 * in your time zone, recomputed in your browser. Change the expression, dialect, or zone to experiment, then copy the result.

Next runs
valid
Upcoming runs
Fri, Jan 1 2027
00:00 UTC
in 55 days
Thu, Apr 1 2027
00:00 UTC
in 145 days
Thu, Jul 1 2027
00:00 UTC
in 236 days
Fri, Oct 1 2027
00:00 UTC
in 328 days
Sat, Jan 1 2028
00:00 UTC
in 420 days
Sat, Apr 1 2028
00:00 UTC
in 511 days
Sat, Jul 1 2028
00:00 UTC
in 602 days
Sun, Oct 1 2028
00:00 UTC
in 694 days
Mon, Jan 1 2029
00:00 UTC
in 786 days
Sun, Apr 1 2029
00:00 UTC
in 876 days
Sun, Jul 1 2029
00:00 UTC
in 967 days
Mon, Oct 1 2029
00:00 UTC
in 1059 days
Tue, Jan 1 2030
00:00 UTC
in 1151 days
Mon, Apr 1 2030
00:00 UTC
in 1241 days
Mon, Jul 1 2030
00:00 UTC
in 1332 days
Tue, Oct 1 2030
00:00 UTC
in 1424 days

What 0 0 1 1,4,7,10 * means

0 0 1 1,4,7,10 * fires on the first day of each calendar quarter, January, April, July, and October, by listing those four months explicitly. Cron's */3 step would also fire every three months, but anchored to month 1 it gives the same quarters, but the explicit list is clearer about intent.

Quarterly jobs handle the cadence that finance and planning live by: quarterly reports, billing for quarterly plans, OKR resets, and compliance checks that recur every three months.

Field-by-field breakdown

Unix cron has five fields. Here is what each one is doing in this expression:

FieldValueMeaning
Minute0minute = 0
Hour0hour = 0
Day of month1day-of-month = 1
Month1,4,7,10the specific values 1,4,7,10 of month
Day of week*every day-of-week

Every quarter in every scheduler

The same cadence written for the seven cron dialects you are most likely to meet. Copy the line for the system you target, the field count and day-of-week numbering differ between them.

SchedulerExpressionCopy
Unix / crontab0 0 1 1,4,7,10 *
GitHub Actions0 0 1 1,4,7,10 *
Kubernetes CronJob0 0 1 1,4,7,10 *
Vercel Cron0 0 1 1,4,7,10 *
Quartz0 0 0 1 1,4,7,10 ? *
Spring0 0 0 1 1,4,7,10 ?
AWS EventBridge0 0 1 1,4,7,10 ? *

When you would use 0 0 1 1,4,7,10 *

The gotcha worth knowing

If your fiscal quarters don't start in January, list your actual quarter-start months (e.g. 2,5,8,11). The default 1,4,7,10 assumes a calendar-aligned fiscal year.

People also search for

cron every quartercron quarterlycrontab every 3 monthscron first of quarter

0 0 1 1,4,7,10 * FAQ

What does the cron expression 0 0 1 1,4,7,10 * mean?

0 0 1 1,4,7,10 * means: Run on the 1st of January, April, July, and October at midnight. 0 0 1 1,4,7,10 * fires on the first day of each calendar quarter, January, April, July, and October, by listing those four months explicitly. Cron's */3 step would also fire every three months, but anchored to month 1 it gives the same quarters, but the explicit list is clearer about intent.

How do I write "every quarter" in GitHub Actions?

Use 0 0 1 1,4,7,10 * in the schedule's cron field. If your fiscal quarters don't start in January, list your actual quarter-start months (e.g. 2,5,8,11). The default 1,4,7,10 assumes a calendar-aligned fiscal year.

How do I write "every quarter" for AWS EventBridge?

EventBridge uses six fields with a required year and a ? placeholder in one day field: 0 0 1 1,4,7,10 ? *. Wrap it as cron(0 0 1 1,4,7,10 ? *) in the console or CloudFormation.

What is the Quartz equivalent of 0 0 1 1,4,7,10 *?

Quartz is seconds-first with a trailing year, so the equivalent is 0 0 0 1 1,4,7,10 ? *. Remember Quartz numbers Sunday as 1, the opposite of Unix.

Related cron patterns

More cron tools

Browse the full set of cron pattern pages, or jump to the interactive tools: the cron expression builder for designing a schedule from scratch, the cron cheat sheet for a side-by-side reference, the cron timezone translator for moving a schedule between zones and dialects, and the GitHub Actions cron picker for DST-stable CI schedules.