Cron every 2 minutes

*/2 selects every even minute from :00 through :58. It is aligned to the clock, so deploying at :01 does not shift the schedule to odd minutes. Expression: */2 * * * *

Use 1-59/2 * * * *. It fires at :01, :03, :05, and every odd minute through :59. Expression: 1-59/2 * * * *

Use */2 9-17 * * 1-5. The inclusive hour range includes 17:00 through 17:58, so use 9-16 if execution must stop before 17:00. Expression: */2 9-17 * * 1-5

No. sleep occupies a worker and can drift under delays; select a stable phase such as 1-59/2 * * * * for odd-minute starts. Expression: 1-59/2 * * * *

Use */2 * * * 1-5. It keeps the two-minute cadence throughout Monday through Friday and does not run on weekends. Expression: */2 * * * 1-5

It is platform-specific. Vixie/cronie can skip or double local two-minute matches; GitHub advances a nonexistent local time; EventBridge Scheduler skips spring and runs once in the fall overlap. UTC-only Vercel and Cloudflare schedules are unaffected.

No. GitHub Actions has a five-minute minimum for scheduled workflows; choose */5 * * * * or use another scheduler. EventBridge's one-minute floor does allow a two-minute schedule. Expression: */5 * * * *

Use cron(0/2 * * * ? *). EventBridge uses six fields including year, requires ? in one day field, and has a one-minute minimum. Expression: 0/2 * * * ? *

Use 0 0/2 * * * ?. The leading field pins seconds to zero, and 0/2 selects even minutes. Expression: 0 0/2 * * * ?

Usually no. Prefer the webhook for prompt delivery and use the two-minute poll only as reconciliation; this cuts 720 baseline requests per day while still repairing missed events.

Budget for at least 720 calls per day before retries. Reserve rate-limit headroom, cap retry attempts, and ensure each run finishes within two minutes; Crontap can run the HTTP schedule with retries.

*/2 * * * *. Paste this into Linux crontab, Vercel cron, node-cron, robfig/cron, or a Kubernetes CronJob to run a job every 2 minutes; AWS EventBridge and Quartz need the six-field form.

The editor above shows the next 30+ runs on a calendar in your local timezone, plus a plain-English description. If the calendar matches your intent, the cron is correct.

Linux crontab, Vercel cron jobs, node-cron, robfig/cron, and Kubernetes CronJob accept the five-field form as is. AWS EventBridge and Quartz use six-field expressions with a ? in one of the day fields; see the AWS and Quartz guides for the conversion. Vercel's free Hobby plan caps the minimum frequency at once-per-day; the Pro plan removes that cap.

Most schedulers will start the new run anyway, leading to overlap. To prevent this, wrap the command with flock -n /tmp/myjob.lock /path/to/script.sh on Linux, or set concurrencyPolicy: Forbid on Kubernetes CronJob. Vercel and EventBridge may overlap runs if the previous one is still executing; make the handler idempotent.