Cron every Sunday
0 9 * * 0At 09:00, only on Sunday.
Next runs · UTC
- —
- —
- —
- —
- —
Calendar
September 2026 · UTC
0 runs
The cron expression for every Sunday at 09:00
0 9 * * 0
The day-of-week value 0 (or 7) is Sunday in standard cron. Quartz uses 1=Sunday - verify the dialect when copying expressions across schedulers.
See the dedicated guide for the full breakdown: Cron every week.
Paste it into the editor above to see the next runs on a calendar.
When to run a job every Sunday at 09:00
- Reports and notifications that should only go out every Sunday at 09:00.
- Maintenance windows and heavier batch jobs scheduled around when people are working.
- Reminders and check-ins tied to a weekly rhythm rather than a calendar date.
Run this cron anywhere
0 9 * * 0 is five-field cron syntax. It works as is in:
- Linux
crontab-0 9 * * 0 /path/to/script.sh - Vercel cron jobs - declare in
vercel.json. - node-cron, robfig/cron and Kubernetes CronJob.
AWS EventBridge and Quartz use six-field expressions with a ? in one of the day fields, so convert first:
- AWS EventBridge -
cron(minute hour day-of-month month ? year); see the AWS guide. - Quartz Scheduler - prepend a seconds field (
0) and replace one day field with?; see the Quartz guide.
Useful variations
0 0 * * 0- every Sunday at midnight (equivalent to @weekly)0 9 * * SUN- name-alias form (equivalent)0 9 * * 7- alternative numeric form (7 = Sunday)
Gotchas when running every Sunday at 09:00
- Timezone and daylight saving - DST handling is scheduler-specific: Vixie/cronie can skip or double local matches; GitHub advances nonexistent local times; EventBridge Scheduler skips spring and runs once in the fall overlap. UTC-only Vercel and Cloudflare schedules are unaffected.
- Missed runs are not replayed - If the host or platform is unavailable at the scheduled minute, standard cron simply waits for the next match. Add a heartbeat or alert if a skipped run must be noticed.
- Day-of-week and day-of-month are OR-ed - In Vixie-style cron, restricting both fields runs the job when either matches. Keep day-of-month as
*when the weekday is the only restriction you want. - Sunday numbering varies by dialect - Vixie-style cron accepts 0 and 7 as Sunday. AWS EventBridge and Quartz use 1 for Sunday and 7 for Saturday; prefer weekday names when translating dialects.
Examples
- 0 18 * * *Every day at 18:00
- 0 */5 * * *Every 5 hours
- 0 18 * * 1-5Weekdays at 18:00
- 0 0 1 * *Once a month, on the 1st at midnight
Cheatsheet
Full cheatsheet| Field | Req. | Range | Wildcards |
|---|---|---|---|
| minute | yes | 0-59 | , - * / |
| hour | yes | 0-23 | , - * / |
| day of month | yes | 1-31 | , - * / |
| month | yes | 1-12 or JAN-DEC | , - * / |
| day of week | yes | 0-6 or names; some dialects use 0-7 or 1-7 — see Dialects | , - * / |
Frequently asked questions
Syntax
Can Sunday be 0 or 7 in crontab?
Yes. Vixie cron accepts both 0 9 * * 0 and 0 9 * * 7 for Sunday; SUN is clearer when weekday names are supported. Expression: 0 9 * * 7
Timing
Why does a weekly cron often use Sunday midnight?
Vixie crontab defines @weekly as Sunday at 00:00. Use 0 0 * * 0 explicitly when readers need to see that boundary. Expression: 0 0 * * 0
How do I schedule a Sunday maintenance window at 02:00?
Use 0 2 * * 0 in Vixie cron. Set a timeout so maintenance cannot run into Monday operations. Expression: 0 2 * * 0
What expression runs every Sunday at midnight?
Use 0 0 * * 0. In Vixie crontab this is also the schedule represented by the @weekly shortcut. Expression: 0 0 * * 0
Days and months
Does 0 9 1 * 0 mean Sunday only when it is the first?
No in Vixie cron. It runs every Sunday and every first day of the month because restricted day fields are OR-ed; Quartz and AWS forbid this combination and require ? in one day field. Expression: 0 9 1 * 0
How do I schedule the second Sunday of each month?
Use 0 0 9 ? * SUN#2 in Quartz-compatible syntax. The name avoids Sunday-number differences across dialects. Expression: 0 0 9 ? * SUN#2
How do I schedule the last Sunday of each month?
Use 0 0 9 ? * SUNL in Quartz-compatible syntax. Standard Vixie crontab does not support weekday L, so it needs a wrapper. Expression: 0 0 9 ? * SUNL
Platforms
Does 0 9 * * 1 mean Sunday or Monday?
The final 1 means Monday in Vixie numbering but Sunday in Quartz numbering; however, the five-field form is invalid in Quartz. For Sunday in Quartz, use 0 0 9 ? * SUN. Expression: 0 0 9 ? * SUN
What is the Quartz form for every Sunday at 09:00?
Use 0 0 9 ? * SUN. Quartz prepends seconds and uses ? for day-of-month; the name avoids numeric ambiguity. Expression: 0 0 9 ? * SUN
Debugging
How do I verify a Sunday schedule does not also run Saturday?
Use one Sunday value, not the weekend list. In Vixie cron, 0 9 * * 0 is Sunday-only, while 0 9 * * 0,6 includes Saturday. Expression: 0 9 * * 0
Crontap
Can Crontap call an endpoint every Sunday?
Yes. Crontap can run 0 9 * * 0 in the selected IANA timezone and invoke an HTTP endpoint every Sunday.
General
What is the cron expression for every Sunday at 09:00?
0 9 * * 0. Paste this into Linux crontab, Vercel cron, node-cron, robfig/cron, or a Kubernetes CronJob to run a job every Sunday at 09:00; AWS EventBridge and Quartz need the six-field form.
How can I verify this cron actually runs every Sunday at 09:00?
The editor above shows the next 30+ runs on a calendar in your local timezone, plus a plain-English description. If the calendar matches your intent, the cron is correct.
Does 0 9 * * 0 work on every platform?
Linux crontab, Vercel cron jobs, node-cron, robfig/cron, and Kubernetes CronJob accept the five-field form as is. AWS EventBridge and Quartz use six-field expressions with a ? in one of the day fields; see the AWS and Quartz guides for the conversion. Vercel's free Hobby plan caps the minimum frequency at once-per-day; the Pro plan removes that cap.
What happens if the previous run is still going when the next one fires?
Most schedulers will start the new run anyway, leading to overlap. To prevent this, wrap the command with flock -n /tmp/myjob.lock /path/to/script.sh on Linux, or set concurrencyPolicy: Forbid on Kubernetes CronJob. Vercel and EventBridge may overlap runs if the previous one is still executing; make the handler idempotent.
Write the cron here. Run it on Crontap.
Point Crontap at any URL. Pick any cron. Done.
WordPress, Shopify, Railway, Cloud Run, Vercel, HubSpot, Ghost, your own box. If it answers HTTP, Crontap can drive it on a clock you can read, in the timezone that actually matters, and page you when something breaks.
1.9k+ teams · Free forever tier · No credit card