Devtools.supstudio.in

Tools/Cron

node-cron cron

The node-cron package schedules callbacks inside a Node process. If the process sleeps, jobs do not run — unlike system crontab. Pass timezone in the options object for wall-clock jobs.

Field format

optional seconds + 5-field crontab

Open the builder

Gotchas

Will node-cron run if my dyno is asleep?
No. You need a process that stays up, or move the schedule to GitHub Actions, Vercel Cron, or a real crontab.
5 or 6 fields?
node-cron accepts both. Six fields start with seconds. Do not mix formats in one codebase.

Examples

Snippet for node-cron

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