Cron Explainer logo
Cron Explainer
ToolsAcademyExamplesPlatformsDocsBlogAboutContact
Back to examples
Days
Easy
Unix / Linux

Cron expression for every Wednesday at 14

Run a scheduled job every Wednesday at 14.

Cron expression0 14 * * 3
Runs every Wednesday at 14.

Primary dialect: Unix / Linux

Next run examples

Static preview generated for the primary dialect. AWS examples use UTC; other examples use Europe/Berlin for display.

Jun 10, 2026, 2:00 PM

Jun 17, 2026, 2:00 PM

Jun 24, 2026, 2:00 PM

Jul 1, 2026, 2:00 PM

Jul 8, 2026, 2:00 PM

Dialect versions

Unix / Linux
0 14 * * 3

Standard Unix/Linux cron expression when this schedule is expressible with five fields.

AWS EventBridge
cron(0 14 ? * WED *)

AWS EventBridge cron schedules are evaluated in UTC. Use rate(...) for simple fixed intervals when possible.

Quartz
0 0 14 ? * WED

Quartz includes a leading seconds field and supports additional day operators.

Kubernetes
0 14 * * 3

Kubernetes CronJobs use standard five-field cron syntax. Non-standard operators require job-level logic.

Variants

Weekday version
0 9 * * 1-5

Runs at 09:00 Monday through Friday.

Daily version
0 0 * * *

Runs every day at midnight.

Hourly version
0 * * * *

Runs once per hour.

Kubernetes notes

  • Kubernetes CronJobs use standard five-field cron syntax.
  • "Set concurrencyPolicy
  • restartPolicy
  • and history limits based on expected runtime and failure behavior."

Common mistakes

  • Forgetting to confirm which timezone the scheduler uses.
  • Assuming the schedule starts relative to deployment time instead of matching wall-clock fields.

FAQ

What is the cron expression for every wednesday at 14?

Use `0 14 * * 3` for standard cron when the scheduler supports this syntax.

Can I use this expression in Kubernetes?

Yes, if it is standard five-field cron. AWS and Quartz-only operators need a Kubernetes-safe alternative or application-level date logic.

Related cron resources