Cron Expression for Every 5 Minutes (*/5 * * * *)
Schedule summary: Every 5 minutes (at :00, :05, :10...). Test live US Eastern, Pacific, and UTC execution timestamps below or copy platform-ready configs.
"Every 5 minutes, every hour, every day"
Next 10 Scheduled Executions
America/New_York- 1Tue, Nov 17, 2026, 09:05 AM EST
- 2Tue, Nov 17, 2026, 09:10 AM EST
- 3Tue, Nov 17, 2026, 09:15 AM EST
- 4Tue, Nov 17, 2026, 09:20 AM EST
- 5Tue, Nov 17, 2026, 09:25 AM EST
- 6Tue, Nov 17, 2026, 09:30 AM EST
- 7Tue, Nov 17, 2026, 09:35 AM EST
- 8Tue, Nov 17, 2026, 09:40 AM EST
- 9Tue, Nov 17, 2026, 09:45 AM EST
- 10Tue, Nov 17, 2026, 09:50 AM EST
Cron Operator Reference
*Any / every value in this field,Value list separator (e.g., 1,15 runs on 1st & 15th)-Inclusive range (e.g., 9-17 means 9 AM through 5 PM)/Step increment (e.g., */10 runs every 10 units)1-5Monday through Friday in Weekday fieldCopy-Ready Snippets for Linux, GitHub Actions, Kubernetes & AWS
*/5 * * * * /usr/local/bin/run-task.sh >> /var/log/task.log 2>&1
on:
schedule:
- cron: '*/5 * * * *' # Runs in UTC apiVersion: batch/v1 kind: CronJob spec: schedule: "*/5 * * * *" timeZone: "America/New_York"
cron(0/5 * * * ? *)
Production Use Cases & Gotchas
- GitHub Actions scheduled workflows (smallest officially supported interval).
- SaaS billing webhook reconciliation and payment status polling.
- Uptime monitoring, log aggregation, and Redis queue draining.
Production Note: GitHub Actions drops or delays */5 * * * * runs during peak UTC top-of-hour minutes—avoid assuming exact second-level precision on shared runners.
Frequently Asked Questions
How do you write a cron expression for every 5 minutes (at :00, :05, :10...)? +
Use the 5-field POSIX cron expression "*/5 * * * *" for Linux crontab, Kubernetes CronJobs, and GitHub Actions. In AWS EventBridge (6-field format), use "cron(0/5 * * * ? *)".
What timezone does */5 * * * * run in on GitHub Actions and AWS? +
GitHub Actions and AWS EventBridge evaluate "*/5 * * * *" strictly in UTC (Coordinated Universal Time). Kubernetes v1.27+ allows setting spec.timeZone (such as "America/New_York").
What is the biggest gotcha with "*/5 * * * *" in production? +
GitHub Actions drops or delays */5 * * * * runs during peak UTC top-of-hour minutes—avoid assuming exact second-level precision on shared runners.