Back to examples
Business Schedules
Easy
Unix / Linux

Cron expression for every 5 minutes during business hours

Run a scheduled job every 5 minutes during weekday business hours.

Cron expression*/5 9-17 * * 1-5
Runs every 5 minutes from 09:00 through 17:59 Monday through Friday.

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 9, 2026, 10:45 AM

Jun 9, 2026, 10:50 AM

Jun 9, 2026, 10:55 AM

Jun 9, 2026, 11:00 AM

Jun 9, 2026, 11:05 AM


Dialect versions

Unix / Linux
*/5 9-17 * * 1-5

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

AWS EventBridge
cron(*/5 9-17 ? * MON-FRI *)

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

Quartz
0 */5 9-17 ? * MON-FRI

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

Kubernetes
*/5 9-17 * * 1-5

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


Variants

Every 10 minutes
*/10 * * * *

Runs at minute 0, 10, 20, 30, 40, and 50.

Every 15 minutes
*/15 * * * *

Runs every quarter hour.

Weekday interval
*/5 * * * 1-5

Runs on weekdays only.


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 5 minutes during business hours?

Use `*/5 9-17 * * 1-5` 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