ClockOrbit

Every N minutes

*/30 * * * *

Run twice an hour, on the hour and the half hour.

This preview is live: the table below shows the actual next run times for */30 * * * * in your time zone, recomputed in your browser. Change the expression, dialect, or zone to experiment, then copy the result.

Next runs
valid
Upcoming runs
Fri, Nov 6 2026
13:30 UTC
in 16 minutes
Fri, Nov 6 2026
14:00 UTC
in 46 minutes
Fri, Nov 6 2026
14:30 UTC
in 1 hours
Fri, Nov 6 2026
15:00 UTC
in 2 hours
Fri, Nov 6 2026
15:30 UTC
in 2 hours
Fri, Nov 6 2026
16:00 UTC
in 3 hours
Fri, Nov 6 2026
16:30 UTC
in 3 hours
Fri, Nov 6 2026
17:00 UTC
in 4 hours
Fri, Nov 6 2026
17:30 UTC
in 4 hours
Fri, Nov 6 2026
18:00 UTC
in 5 hours
Fri, Nov 6 2026
18:30 UTC
in 5 hours
Fri, Nov 6 2026
19:00 UTC
in 6 hours
Fri, Nov 6 2026
19:30 UTC
in 6 hours
Fri, Nov 6 2026
20:00 UTC
in 7 hours
Fri, Nov 6 2026
20:30 UTC
in 7 hours
Fri, Nov 6 2026
21:00 UTC
in 8 hours
Fri, Nov 6 2026
21:30 UTC
in 8 hours
Fri, Nov 6 2026
22:00 UTC
in 9 hours
Fri, Nov 6 2026
22:30 UTC
in 9 hours
Fri, Nov 6 2026
23:00 UTC
in 10 hours
Fri, Nov 6 2026
23:30 UTC
in 10 hours
Sat, Nov 7 2026
00:00 UTC
in 11 hours
Sat, Nov 7 2026
00:30 UTC
in 11 hours
Sat, Nov 7 2026
01:00 UTC
in 12 hours
Sat, Nov 7 2026
01:30 UTC
in 12 hours

What */30 * * * * means

*/30 * * * * fires on the hour and the half-hour, 48 times a day. It is the lightest sub-hourly cadence, frequent enough to keep data reasonably fresh, sparse enough that overlap is almost never a problem.

Half-hourly is the typical home for jobs that are mildly expensive: digest emails that batch the last 30 minutes of activity, partial reindexes, or syncs against APIs with tight rate limits. It is also a sensible default when you are not sure how often you need to run and want to start conservative.

Field-by-field breakdown

Unix cron has five fields. Here is what each one is doing in this expression:

FieldValueMeaning
Minute*/30every 30 (step) across minute
Hour*every hour
Day of month*every day-of-month
Month*every month
Day of week*every day-of-week

Every 30 minutes in every scheduler

The same cadence written for the seven cron dialects you are most likely to meet. Copy the line for the system you target, the field count and day-of-week numbering differ between them.

SchedulerExpressionCopy
Unix / crontab*/30 * * * *
GitHub Actions*/30 * * * *
Kubernetes CronJob*/30 * * * *
Vercel Cron*/30 * * * *
Quartz0 */30 * * * * *
Spring0 */30 * * * *
AWS EventBridge*/30 * * * * *

When you would use */30 * * * *

The gotcha worth knowing

*/30 and 0,30 * * * * are equivalent. People sometimes write 30 * * * * meaning "every 30 minutes", but that fires only once an hour, at :30. Watch the field position.

People also search for

cron every 30 minutes*/30 cron expressioncrontab every half hourcron every 30 min

*/30 * * * * FAQ

What does the cron expression */30 * * * * mean?

*/30 * * * * means: Run twice an hour, on the hour and the half hour. */30 * * * * fires on the hour and the half-hour, 48 times a day. It is the lightest sub-hourly cadence, frequent enough to keep data reasonably fresh, sparse enough that overlap is almost never a problem.

How do I write "every 30 minutes" in GitHub Actions?

Use */30 * * * * in the schedule's cron field. */30 and 0,30 * * * * are equivalent. People sometimes write 30 * * * * meaning "every 30 minutes", but that fires only once an hour, at :30. Watch the field position.

How do I write "every 30 minutes" for AWS EventBridge?

EventBridge uses six fields with a required year and a ? placeholder in one day field: */30 * * * * *. Wrap it as cron(*/30 * * * * *) in the console or CloudFormation.

What is the Quartz equivalent of */30 * * * *?

Quartz is seconds-first with a trailing year, so the equivalent is 0 */30 * * * * *. Remember Quartz numbers Sunday as 1, the opposite of Unix.

Related cron patterns

More cron tools

Browse the full set of cron pattern pages, or jump to the interactive tools: the cron expression builder for designing a schedule from scratch, the cron cheat sheet for a side-by-side reference, the cron timezone translator for moving a schedule between zones and dialects, and the GitHub Actions cron picker for DST-stable CI schedules.