Curated cron expression
Every Wednesday at Noon: 0 12 * * 3
0 12 * * 3 — mid-week midday schedule.
Meaning at a glance
0 12 * * 3
Run every Wednesday at 12:00
Weekly Wednesday at 12:00.
Next-run example: On Thursday, next run is next Wednesday 12:00.
How 0 12 * * 3 works
Wednesday (3) at noon for mid-week operational tasks.
Useful for mid-sprint checkpoints.
Preview next runs and platform conversions in CronWizard before deploying to production.
| Field | Value | Meaning |
|---|---|---|
| Minute | 0 | Configured as 0 |
| Hour | 12 | Configured as 12 |
| Day of month | * | Every value |
| Month | * | Every value |
| Day of week | 3 | Configured as 3 |
Good use cases
- Mid-week reports
- Compliance checks
- Team reminders
Timezone and daylight-saving behavior
Explicit timezone for global teams.
Standard weekly local-time notes.
The expression does not contain a timezone. The scheduler supplies that context. Use the next-run preview above in the same IANA timezone as production, then confirm the target platform's own timezone rules.
Platform compatibility and converted expressions
The source expression is five-field Unix cron. Use the exact equivalent below rather than adding or removing fields by sight.
| Platform | Status | Expression | What to know |
|---|---|---|---|
| Unix crontab | Ready | 0 12 * * 3 | Use directly in a normal five-field user crontab. |
| Kubernetes CronJob | Ready | 0 12 * * 3 | Use as spec.schedule; set spec.timeZone when local wall-clock behavior matters. |
| GitHub Actions | Ready | 0 12 * * 3 | Use under on.schedule; UTC is the default and an IANA timezone may be specified. |
| Vercel Cron Jobs | Plan / behavior limit | 0 12 * * 3 | The expression is valid, but Vercel always uses UTC and Hobby schedules run at most once per day. |
| AWS EventBridge Scheduler | Convert | cron(0 12 ? * 3 *) | Convert to AWS minute-first cron(...), add the required year, and use ? in one day field. |
| Spring @Scheduled | Convert | 0 0 12 * * 3 | Use Spring’s six fields by prepending seconds and set zone explicitly when needed. |
| systemd timer | Convert | 0 12 * * 3 | Use OnCalendar syntax and validate it with systemd-analyze calendar on the target host. |
Edge cases to check before deployment
- 3 = Wednesday.
Frequently asked questions
What does the cron expression 0 12 * * 3 mean?
0 12 * * 3 means “run every wednesday at 12:00.” Weekly Wednesday at 12:00.
What are the next run times for 0 12 * * 3?
On Thursday, next run is next Wednesday 12:00. Exact timestamps depend on the scheduler timezone and the current time.
What timezone does 0 12 * * 3 use?
Explicit timezone for global teams.
Can I use 0 12 * * 3 on every scheduling platform?
No. It is a five-field Unix expression. Some platforms accept it directly, while AWS EventBridge Scheduler, Spring, and systemd require the converted form shown in the compatibility table.