ClockOrbit

Every N minutes

*/2 * * * *

Run on even minutes, :00, :02, :04, … :58.

This preview is live: the table below shows the actual next run times for */2 * * * * 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:14 UTC
in 0 minutes
Fri, Nov 6 2026
13:16 UTC
in 2 minutes
Fri, Nov 6 2026
13:18 UTC
in 4 minutes
Fri, Nov 6 2026
13:20 UTC
in 6 minutes
Fri, Nov 6 2026
13:22 UTC
in 8 minutes
Fri, Nov 6 2026
13:24 UTC
in 10 minutes
Fri, Nov 6 2026
13:26 UTC
in 12 minutes
Fri, Nov 6 2026
13:28 UTC
in 14 minutes
Fri, Nov 6 2026
13:30 UTC
in 16 minutes
Fri, Nov 6 2026
13:32 UTC
in 18 minutes
Fri, Nov 6 2026
13:34 UTC
in 20 minutes
Fri, Nov 6 2026
13:36 UTC
in 22 minutes
Fri, Nov 6 2026
13:38 UTC
in 24 minutes
Fri, Nov 6 2026
13:40 UTC
in 26 minutes
Fri, Nov 6 2026
13:42 UTC
in 28 minutes
Fri, Nov 6 2026
13:44 UTC
in 30 minutes
Fri, Nov 6 2026
13:46 UTC
in 32 minutes
Fri, Nov 6 2026
13:48 UTC
in 34 minutes
Fri, Nov 6 2026
13:50 UTC
in 36 minutes
Fri, Nov 6 2026
13:52 UTC
in 38 minutes
Fri, Nov 6 2026
13:54 UTC
in 40 minutes
Fri, Nov 6 2026
13:56 UTC
in 42 minutes
Fri, Nov 6 2026
13:58 UTC
in 44 minutes
Fri, Nov 6 2026
14:00 UTC
in 46 minutes
Fri, Nov 6 2026
14:02 UTC
in 48 minutes

What */2 * * * * means

*/2 * * * * uses a step value: */2 in the minute field means "start at minute 0 and fire every 2 minutes thereafter", landing on every even minute of every hour. It is a common middle ground for pollers that need to feel responsive without the load of an every-minute job.

Steps are anchored to the start of the range, not to when you deploy. */2 always fires on even minutes regardless of when the crontab was installed, so two jobs both set to */2 will collide on the same even minutes unless you offset one of them with an explicit start like 1-59/2.

Field-by-field breakdown

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

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

Every 2 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*/2 * * * *
GitHub Actions*/2 * * * *
Kubernetes CronJob*/2 * * * *
Vercel Cron*/2 * * * *
Quartz0 */2 * * * * *
Spring0 */2 * * * *
AWS EventBridge*/2 * * * * *

When you would use */2 * * * *

The gotcha worth knowing

*/2 is not "every 2 minutes from now", it is anchored to :00. If you need to stagger two such jobs, use 1-59/2 for the second one so they land on odd minutes.

People also search for

cron every 2 minutes*/2 croncrontab every two minutescron every other minute

*/2 * * * * FAQ

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

*/2 * * * * means: Run on even minutes, :00, :02, :04, … :58. */2 * * * * uses a step value: */2 in the minute field means "start at minute 0 and fire every 2 minutes thereafter", landing on every even minute of every hour. It is a common middle ground for pollers that need to feel responsive without the load of an every-minute job.

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

Use */2 * * * * in the schedule's cron field. */2 is not "every 2 minutes from now", it is anchored to :00. If you need to stagger two such jobs, use 1-59/2 for the second one so they land on odd minutes.

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

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

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

Quartz is seconds-first with a trailing year, so the equivalent is 0 */2 * * * * *. 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.