Every 5 Minutes Cron Expression
*/5 * * * *Try it live
Valid
MINMinute
0HRHour
9DOMDay of Month
*MONMonth
*DOWDay of Week
1-5In plain English
At 09:00 AM, Monday through Friday
English → Cron
Try: "every 5 minutes", "every weekday at 9am", "every Monday at 3pm", "every month on the 1st"
Next 10 Executions
UTC- 1Mon, May 18, 09:00 AM UTCin 3d
- 2Tue, May 19, 09:00 AM UTCin 4d
- 3Wed, May 20, 09:00 AM UTCin 5d
- 4Thu, May 21, 09:00 AM UTCin 6d
- 5Fri, May 22, 09:00 AM UTCin 7d
- 6Mon, May 25, 09:00 AM UTCin 10d
- 7Tue, May 26, 09:00 AM UTCin 11d
- 8Wed, May 27, 09:00 AM UTCin 12d
- 9Thu, May 28, 09:00 AM UTCin 13d
- 10Fri, May 29, 09:00 AM UTCin 14d
crontab entrybash
# Add to crontab with: crontab -e
0 9 * * 1-5 /path/to/your/script.shWhen to use this schedule
- ▸ Caching layers that need periodic refreshes without hammering the database every minute
- ▸ Metrics aggregation pipelines that batch 5-minute windows for dashboards
- ▸ Webhook retry queues that back off to 5-minute intervals after an initial failure
- ▸ Token refresh jobs for OAuth clients that have 10-minute expiry windows
- ▸ Polling external services for status updates where 1-minute latency is acceptable
Platform Syntax Comparison
The same "Every 5 Minutes" schedule expressed in every major platform's cron syntax.
| Platform | Expression |
|---|---|
| Standard Linux/Unix | */5 * * * * |
| GitHub Actions | */5 * * * * |
| Google Cloud Scheduler | */5 * * * * |
| Kubernetes CronJob | */5 * * * * |
| Azure Functions (NCRONTAB) | 0 */5 * * * * |
| AWS EventBridge | 0/5 * * * ? * |
| Quartz Scheduler | 0 */5 * * * ? |
| Spring @Scheduled | 0 */5 * * * * |
| Jenkins | H/5 * * * * |
| Apache Airflow | */5 * * * * |
Frequently Asked Questions
Does */5 run at :00, :05, :10, :15... exactly? ▾
Yes — it triggers at minute 0, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, and 55 of every hour. Always on 5-minute boundaries from the top of the hour.
Why does AWS use "0/5" instead of "*/5"? ▾
AWS EventBridge treats "*/5" and "0/5" identically in the minute field. "0/5" is the explicit form meaning "starting at 0, every 5 minutes" — both are valid.
Why does Jenkins use "H/5" instead of "*/5"? ▾
Jenkins's H (hash) token spreads builds across agents. "H/5" picks a consistent-but-arbitrary starting minute per job to avoid thundering herd at :00.