Cron Expression for Every 30 Minutes (*/30 * * * *)
Schedule summary: Every 30 minutes (:00 and :30 past each hour). Test live US Eastern, Pacific, and UTC execution timestamps below or copy platform-ready configs.
"Every 30 minutes, every hour, every day"
Next 10 Scheduled Executions
America/New_York- 1Tue, Nov 17, 2026, 09:30 AM EST
- 2Tue, Nov 17, 2026, 10:00 AM EST
- 3Tue, Nov 17, 2026, 10:30 AM EST
- 4Tue, Nov 17, 2026, 11:00 AM EST
- 5Tue, Nov 17, 2026, 11:30 AM EST
- 6Tue, Nov 17, 2026, 12:00 PM EST
- 7Tue, Nov 17, 2026, 12:30 PM EST
- 8Tue, Nov 17, 2026, 01:00 PM EST
- 9Tue, Nov 17, 2026, 01:30 PM EST
- 10Tue, Nov 17, 2026, 02:00 PM 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
*/30 * * * * /usr/local/bin/run-task.sh >> /var/log/task.log 2>&1
on:
schedule:
- cron: '*/30 * * * *' # Runs in UTC apiVersion: batch/v1 kind: CronJob spec: schedule: "*/30 * * * *" timeZone: "America/New_York"
cron(0,30 * * * ? *)
Production Use Cases & Gotchas
- Half-hourly analytics warehouse rollups and search index updates.
- Renewing short-lived OAuth provider tokens ahead of expiration.
- Inventory and pricing feed synchronization for US e-commerce stores.
Production Note: To reduce load spikes at :00 and :30 across fleet nodes, shift the minute field to an offset like 7,37 * * * *.
Frequently Asked Questions
How do you write a cron expression for every 30 minutes (:00 and :30 past each hour)? +
Use the 5-field POSIX cron expression "*/30 * * * *" for Linux crontab, Kubernetes CronJobs, and GitHub Actions. In AWS EventBridge (6-field format), use "cron(0,30 * * * ? *)".
What timezone does */30 * * * * run in on GitHub Actions and AWS? +
GitHub Actions and AWS EventBridge evaluate "*/30 * * * *" strictly in UTC (Coordinated Universal Time). Kubernetes v1.27+ allows setting spec.timeZone (such as "America/New_York").
What is the biggest gotcha with "*/30 * * * *" in production? +
To reduce load spikes at :00 and :30 across fleet nodes, shift the minute field to an offset like 7,37 * * * *.