Run 1
Jun 27, 2026, 00:30:00 GMT
Cron preset
Every 30 minutes cron
*/30 * * * * means runs twice per hour, at minute 0 and minute 30.
Meaning
Every 30 minutes
Run 1 · Asia/Shanghai
Jun 27, 2026, 22:30:00 GMT+8
2026-06-27T14:30:00.000Z
Run 2 · Asia/Shanghai
Jun 27, 2026, 23:00:00 GMT+8
2026-06-27T15:00:00.000Z
Run 3 · Asia/Shanghai
Jun 27, 2026, 23:30:00 GMT+8
2026-06-27T15:30:00.000Z
Run 4 · Asia/Shanghai
Jun 28, 2026, 00:00:00 GMT+8
2026-06-27T16:00:00.000Z
Run 5 · Asia/Shanghai
Jun 28, 2026, 00:30:00 GMT+8
2026-06-27T16:30:00.000Z
Upcoming UTC examples
Run 2
Jun 27, 2026, 01:00:00 GMT
Run 3
Jun 27, 2026, 01:30:00 GMT
Run 4
Jun 27, 2026, 02:00:00 GMT
Run 5
Jun 27, 2026, 02:30:00 GMT
How to use it
Useful when hourly is too slow but five-minute polling is excessive.
Use */10 for a ten-minute cadence.
Always confirm the scheduler time zone. A daily or weekly cron can move relative to UTC when the local zone enters or leaves daylight saving time.
Frequently asked questions
What cron expression means every 30 minutes?
Use */30 * * * *. Runs twice per hour, at minute 0 and minute 30.
Which time zone does this cron use?
The scheduler decides the time zone. Preview the expression in TimeKit with the same IANA time zone your server or job runner uses.
Can daylight saving time affect this schedule?
Yes. Schedules tied to local hours can shift relative to UTC when the selected zone enters or leaves daylight saving time.