Cron Expression for Every 15 Minutes (*/15 * * * *)
Schedule summary: Every 15 minutes (:00, :15, :30, :45). Test live US Eastern, Pacific, and UTC execution timestamps below or copy platform-ready configs.
"Every 15 minutes, every hour, every day"
Next 10 Scheduled Executions
America/New_York- 1Tue, Nov 17, 2026, 09:15 AM EST
- 2Tue, Nov 17, 2026, 09:30 AM EST
- 3Tue, Nov 17, 2026, 09:45 AM EST
- 4Tue, Nov 17, 2026, 10:00 AM EST
- 5Tue, Nov 17, 2026, 10:15 AM EST
- 6Tue, Nov 17, 2026, 10:30 AM EST
- 7Tue, Nov 17, 2026, 10:45 AM EST
- 8Tue, Nov 17, 2026, 11:00 AM EST
- 9Tue, Nov 17, 2026, 11:15 AM EST
- 10Tue, Nov 17, 2026, 11:30 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
*/15 * * * * /usr/local/bin/run-task.sh >> /var/log/task.log 2>&1
on:
schedule:
- cron: '*/15 * * * *' # Runs in UTC apiVersion: batch/v1 kind: CronJob spec: schedule: "*/15 * * * *" timeZone: "America/New_York"
cron(0/15 * * * ? *)
Production Use Cases & Gotchas
- Incremental ETL data syncs from Stripe, HubSpot, or Shopify into Postgres.
- Refreshing materialized database views without overwhelming primary replicas.
- Sending batched customer digest notifications.
Production Note: Combine with a weekday business-hours range (*/15 9-17 * * 1-5) when syncing US financial or CRM APIs only during office hours.
Frequently Asked Questions
How do you write a cron expression for every 15 minutes (:00, :15, :30, :45)? +
Use the 5-field POSIX cron expression "*/15 * * * *" for Linux crontab, Kubernetes CronJobs, and GitHub Actions. In AWS EventBridge (6-field format), use "cron(0/15 * * * ? *)".
What timezone does */15 * * * * run in on GitHub Actions and AWS? +
GitHub Actions and AWS EventBridge evaluate "*/15 * * * *" strictly in UTC (Coordinated Universal Time). Kubernetes v1.27+ allows setting spec.timeZone (such as "America/New_York").
What is the biggest gotcha with "*/15 * * * *" in production? +
Combine with a weekday business-hours range (*/15 9-17 * * 1-5) when syncing US financial or CRM APIs only during office hours.