Cron for every Wednesday at 9pm
0 21 * * 3At 09:00 PM, only on Wednesday
What this schedule does
Pin a job to Wednesday at 9pm with 0 21 * * 3. 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.
- Wed, 26 Aug 2026, 21:00 UTC
- Wed, 02 Sept 2026, 21:00 UTC
- Wed, 09 Sept 2026, 21:00 UTC
- Wed, 16 Sept 2026, 21:00 UTC
- Wed, 23 Sept 2026, 21:00 UTC
Copy-paste snippets
GitHub Actions
UTC only. Quote the expression so YAML keeps the stars.
on:
schedule:
- cron: '0 21 * * 3'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 21 * * 3"
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 21 ? * 3 *)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 21 * * 3Vercel Cron
{
"crons": [
{
"path": "/api/cron",
"schedule": "0 21 * * 3"
}
]
}crontab
0 21 * * 3 /usr/local/bin/jobnode-cron
import cron from 'node-cron';
cron.schedule('0 21 * * 3', () => {
// job
});Spring @Scheduled
Spring uses 6 fields by default (seconds first) unless you set spring.task.scheduling.cron.expression.
@Scheduled(cron = "0 0 21 * * 3")
public void run() {
// job
}