Devtools.supstudio.in

Tools/Cron

Cron for the first day of each quarter at midnight

0 0 1 1,4,7,10 *

At 12:00 AM, on day 1 of the month, only in January, April, July, and October

Open in builder

What this schedule does

0 0 1 1,4,7,10 * is midnight on 1 Jan, 1 Apr, 1 Jul, and 1 Oct. Quarterly close, VAT cycles, and OKR resets map cleanly onto those four month numbers.

Next 5 runs (UTC)

Times below are computed for UTC. Open the builder to preview another timezone.

  1. Thu, 01 Oct 2026, 00:00 UTC
  2. Fri, 01 Jan 2027, 00:00 UTC
  3. Thu, 01 Apr 2027, 00:00 UTC
  4. Thu, 01 Jul 2027, 00:00 UTC
  5. Fri, 01 Oct 2027, 00:00 UTC

Copy-paste snippets

GitHub Actions

UTC only. Quote the expression so YAML keeps the stars.

on:
  schedule:
    - cron: '0 0 1 1,4,7,10 *'

Kubernetes

CronJob spec.schedule. Kubernetes uses the timezone of the kube-controller-manager unless you set .spec.timeZone.

apiVersion: batch/v1
kind: CronJob
metadata:
  name: job
spec:
  schedule: "0 0 1 1,4,7,10 *"
  jobTemplate:
    spec:
      template:
        spec:
          restartPolicy: OnFailure
          containers:
            - name: job
              image: busybox
              args: ["echo", "run"]

AWS EventBridge

Six fields: minutes hours day-of-month month day-of-week year. Use ? in either day-of-month or day-of-week.

cron(0 0 1 1,4,7,10 ? *)

Quartz

Quartz is seconds-first (6 or 7 fields). Day-of-week names are MON, TUE, … and ? is required in one of the day fields.

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

Vercel Cron

{
  "crons": [
    {
      "path": "/api/cron",
      "schedule": "0 0 1 1,4,7,10 *"
    }
  ]
}

crontab

0 0 1 1,4,7,10 * /usr/local/bin/job

node-cron

import cron from 'node-cron';

cron.schedule('0 0 1 1,4,7,10 *', () => {
  // job
});

Spring @Scheduled

Spring uses 6 fields by default (seconds first) unless you set spring.task.scheduling.cron.expression.

@Scheduled(cron = "0 0 0 1 1,4,7,10 *")
public void run() {
    // job
}

Related schedules

    Platform guides