Devtools.supstudio.in

Tools/Cron

Spring cron

Spring Framework's @Scheduled annotation uses a 6-field cron string by default (seconds minutes hours day-of-month month day-of-week). You can pass zone = "Asia/Kolkata" so the clock is not the server default.

Field format

second minute hour day-of-month month day-of-week

Open the builder

Gotchas

Why did my 5-field crontab fail in Spring?
Spring expects seconds. Prefix 0. 0 9 * * MON is invalid; use 0 0 9 * * MON.
How do I run on weekdays only?
0 0 9 * * MON-FRI with zone set, or 0 0 9 * * 1-5 depending on your Spring version's day numbering.

Examples

Snippet for Spring

GitHub Actions

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

on:
  schedule:
    - cron: '0 9 * * 1'

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 9 * * 1"
  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 9 ? * 1 *)

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 9 * * 1

Vercel Cron

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

crontab

0 9 * * 1 /usr/local/bin/job

node-cron

import cron from 'node-cron';

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

Spring @Scheduled

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

@Scheduled(cron = "0 0 9 * * 1")
public void run() {
    // job
}

Useful schedules

Other platforms