Cron for 1 october at 9am
0 9 1 10 *At 09:00 AM, on day 1 of the month, only in October
What this schedule does
0 9 1 10 * is 09:00 on the first of october. Business-hours yearly jobs (compliance reports, insurance statements) should not run at midnight when nobody is watching logs.
Next 5 runs (UTC)
Times below are computed for UTC. Open the builder to preview another timezone.
- Thu, 01 Oct 2026, 09:00 UTC
- Fri, 01 Oct 2027, 09:00 UTC
- Sun, 01 Oct 2028, 09:00 UTC
- Mon, 01 Oct 2029, 09:00 UTC
- Tue, 01 Oct 2030, 09:00 UTC
Copy-paste snippets
GitHub Actions
UTC only. Quote the expression so YAML keeps the stars.
on:
schedule:
- cron: '0 9 1 10 *'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 10 *"
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 10 ? *)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 10 *Vercel Cron
{
"crons": [
{
"path": "/api/cron",
"schedule": "0 9 1 10 *"
}
]
}crontab
0 9 1 10 * /usr/local/bin/jobnode-cron
import cron from 'node-cron';
cron.schedule('0 9 1 10 *', () => {
// 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 10 *")
public void run() {
// job
}