Devtools.supstudio.in

Tools/Cron

Cron for every Saturday at noon

0 12 * * 6

At 12:00 PM, only on Saturday

Open in builder

What this schedule does

Pin a job to Saturday at noon with 0 12 * * 6. Weekly deploys, payroll exports, and newsletter sends almost always name a weekday rather than “every 7 days,” because wall-clock day-of-week survives DST better than a raw interval.

Next 5 runs (UTC)

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

  1. Sat, 22 Aug 2026, 12:00 UTC
  2. Sat, 29 Aug 2026, 12:00 UTC
  3. Sat, 05 Sept 2026, 12:00 UTC
  4. Sat, 12 Sept 2026, 12:00 UTC
  5. Sat, 19 Sept 2026, 12:00 UTC

Copy-paste snippets

GitHub Actions

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

on:
  schedule:
    - cron: '0 12 * * 6'

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 12 * * 6"
  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 12 ? * 6 *)

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 12 * * 6

Vercel Cron

{
  "crons": [
    {
      "path": "/api/cron",
      "schedule": "0 12 * * 6"
    }
  ]
}

crontab

0 12 * * 6 /usr/local/bin/job

node-cron

import cron from 'node-cron';

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

Spring @Scheduled

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

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

Related schedules

Platform guides