Every 30 Minutes Cron Expression
*/30 * * * *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
- ▸ Half-hourly data syncs between a transactional database and a reporting replica
- ▸ Email digest jobs that batch notifications into half-hour windows
- ▸ Polling a partner API that updates on a 30-minute cadence
- ▸ Backup jobs for small databases where hourly is too infrequent and per-minute is overkill
Platform Syntax Comparison
The same "Every 30 Minutes" schedule expressed in every major platform's cron syntax.
| Platform | Expression |
|---|---|
| Standard Linux/Unix | */30 * * * * |
| GitHub Actions | */30 * * * * |
| Google Cloud Scheduler | */30 * * * * |
| Kubernetes CronJob | */30 * * * * |
| Azure Functions (NCRONTAB) | 0 */30 * * * * |
| AWS EventBridge | 0/30 * * * ? * |
| Quartz Scheduler | 0 */30 * * * ? |
| Spring @Scheduled | 0 */30 * * * * |
| Jenkins | H/30 * * * * |
| Apache Airflow | */30 * * * * |
Frequently Asked Questions
What are the exact run times for */30? ▾
"*/30" fires at :00 and :30 of every hour — twice per hour.
Is "0,30 * * * *" the same as "*/30 * * * *"? ▾
Functionally yes — both fire at :00 and :30 each hour. The comma form is more explicit and sometimes preferred for readability.