Devtools.supstudio.in

Tools/Cron

Cron for every day at 8am thirty

30 8 * * *

At 08:30 AM, every day

Open in builder

What this schedule does

Thirty minutes past 8am uses 30 8 * * *. The half-hour offset is a cheap way to miss the :00 pile-up on shared CI. Nightly maintenance that should not start exactly at midnight often lands here.

Next 5 runs (UTC)

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

  1. Fri, 21 Aug 2026, 08:30 UTC
  2. Sat, 22 Aug 2026, 08:30 UTC
  3. Sun, 23 Aug 2026, 08:30 UTC
  4. Mon, 24 Aug 2026, 08:30 UTC
  5. Tue, 25 Aug 2026, 08:30 UTC

Copy-paste snippets

GitHub Actions

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

on:
  schedule:
    - cron: '30 8 * * *'

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: "30 8 * * *"
  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(30 8 * * ? *)

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 30 8 * * *

Vercel Cron

{
  "crons": [
    {
      "path": "/api/cron",
      "schedule": "30 8 * * *"
    }
  ]
}

crontab

30 8 * * * /usr/local/bin/job

node-cron

import cron from 'node-cron';

cron.schedule('30 8 * * *', () => {
  // job
});

Spring @Scheduled

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

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

Related schedules

Platform guides