Cron every Tuesday
0 9 * * 2At 09:00, only on Tuesday.
Next runs · UTC
- —
- —
- —
- —
- —
Calendar
September 2026 · UTC
0 runs
About this tool
0 9 * * 2. Useful for weekly tasks that should land mid-week instead of on Monday - when Monday is too noisy or already booked with a separate weekly job.The cron expression for every Tuesday at 09:00
0 9 * * 2
The day-of-week value 2 is Tuesday in standard cron. Name-alias form: 0 9 * * TUE.
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 Tuesday at 09:00
- Reports and notifications that should only go out every Tuesday 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 * * 2 is five-field cron syntax. It works as is in:
- Linux
crontab-0 9 * * 2 /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 * * 2- every Tuesday at midnight0 9 * * TUE- name-alias form (equivalent)0 9 * * 2,5- Tuesday and Friday - twice-a-week pattern
Gotchas when running every Tuesday 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 I write TUE instead of 2 for Tuesday?
Yes. 0 9 * * TUE is equivalent to 0 9 * * 2 in schedulers that accept weekday names. Expression: 0 9 * * TUE
How do I run on Tuesday and Friday?
Use 0 9 * * 2,5. The comma creates a day-of-week list without implying an interval between runs. Expression: 0 9 * * 2,5
Timing
What cron works for a Tuesday release train at 14:00?
Use 0 14 * * 2. Tuesday avoids Monday's backlog while leaving several weekdays for monitoring and rollback. Expression: 0 14 * * 2
Why schedule weekly processing on Tuesday instead of Monday?
Tuesday gives Monday ingestion and backlog jobs time to finish. Use 0 9 * * 2 after verifying upstream data is complete. Expression: 0 9 * * 2
Days and months
Does 0 9 1 * 2 mean Tuesday only when it is the first?
No in Vixie cron. It fires on every Tuesday and every first day of the month because restricted day fields are OR-ed; Quartz and AWS require one day field to be ?. Expression: 0 9 1 * 2
How do I schedule the second Tuesday of each month?
Use 0 0 9 ? * TUE#2 in Quartz-compatible syntax. It matches the second Tuesday, a common Patch Tuesday maintenance window; Vixie cron needs a wrapper. Expression: 0 0 9 ? * TUE#2
How do I schedule the last Tuesday of each month?
Use 0 0 9 ? * TUEL in Quartz-compatible syntax. Vixie crontab lacks this weekday L operator, so use a wrapper there. Expression: 0 0 9 ? * TUEL
Are Tuesday and Friday runs equally spaced?
No. 0 9 * * 2,5 has a three-day Tuesday-to-Friday gap and a four-day Friday-to-Tuesday gap. Expression: 0 9 * * 2,5
Platforms
What is the Quartz form for every Tuesday at 09:00?
Use 0 0 9 ? * TUE. Quartz requires a leading seconds field and leaves day-of-month unspecified with ?. Expression: 0 0 9 ? * TUE
Debugging
Should a Patch Tuesday cron assume a reboot completed?
No. Cron only starts by time; make patch completion or reboot health an explicit prerequisite before dependent Tuesday jobs continue.
Crontap
Can Crontap call an endpoint every Tuesday?
Yes. Crontap can run 0 9 * * 2 in the selected IANA timezone and invoke an HTTP endpoint every Tuesday.
General
What is the cron expression for every Tuesday at 09:00?
0 9 * * 2. Paste this into Linux crontab, Vercel cron, node-cron, robfig/cron, or a Kubernetes CronJob to run a job every Tuesday at 09:00; AWS EventBridge and Quartz need the six-field form.
How can I verify this cron actually runs every Tuesday 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 * * 2 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