Aarunya AppsAarunya Apps

Every Quarter Cron Expression — 0 0 1 */3 *

Cron Expression

0 0 1 */3 *

What it means

Runs on the 1st of January, April, July, and October

Used for quarterly financial reports, SOC 2 evidence collection automation, clearing long-lived caches, or triggering compliance review workflows.

Next 8 Scheduled Runs (UTC)

  1. 1.Wed, 01 Jul 2026 00:00:00 GMT
  2. 2.Thu, 01 Oct 2026 00:00:00 GMT
  3. 3.Fri, 01 Jan 2027 00:00:00 GMT
  4. 4.Thu, 01 Apr 2027 00:00:00 GMT
  5. 5.Thu, 01 Jul 2027 00:00:00 GMT
  6. 6.Fri, 01 Oct 2027 00:00:00 GMT
  7. 7.Sat, 01 Jan 2028 00:00:00 GMT
  8. 8.Sat, 01 Apr 2028 00:00:00 GMT

Platform Snippets

GitHub Actions

- cron: '0 0 1 */3 *'

Kubernetes CronJob

schedule: "0 0 1 */3 *"

AWS EventBridge

cron(0 0 1 */3 ? *)

AWS uses a 6-field format with year and requires either DOM or DOW to be ?.

systemd Timer

[Timer]
OnCalendar=*-*-1 00:00:00
Persistent=true

Want to decode a different expression or test your own?

Test this expression interactively →

FAQ

What does the cron expression 0 0 1 */3 * mean?

Runs on the 1st of January, April, July, and October. Used for quarterly financial reports, SOC 2 evidence collection automation, clearing long-lived caches, or triggering compliance review workflows.

How do I use 0 0 1 */3 * in GitHub Actions?

Add a schedule trigger under the "on" key in your workflow YAML: on: schedule: - cron: '0 0 1 */3 *'. This will run your workflow runs on the 1st of january, april, july, and october. Note that GitHub Actions uses UTC time.

Is the cron expression 0 0 1 */3 * valid for Kubernetes CronJobs?

Yes. Set the schedule field in your CronJob spec to "0 0 1 */3 *". Kubernetes CronJobs use standard 5-field cron syntax and run in UTC by default unless you configure a timeZone field.