Cron every 10 minutes

Six times: :00, :10, :20, :30, :40, and :50. That is 144 runs in a 24-hour day, aligned to minute zero rather than deployment time. Expression: */10 * * * *

Use 5-59/10 * * * *. It fires at :05, :15, :25, :35, :45, and :55, while keeping ten-minute spacing. Expression: 5-59/10 * * * *

Use */10 9-17 * * 1-5. It runs six times in each included hour from Monday through Friday, and the inclusive range also includes the 17:00 hour. Expression: */10 9-17 * * 1-5

It processes roughly twice the records per run of a five-minute poll at the same arrival rate, while halving starts from 288 to 144 daily. Size timeouts and page limits accordingly.

Use */10 * * * 1-5. The minute cadence continues through every hour on Monday through Friday and stops on Saturday and Sunday. Expression: */10 * * * 1-5

It varies by platform. Vixie/cronie can skip or double local ten-minute matches; GitHub advances nonexistent local times; EventBridge Scheduler skips spring and runs once in the fall overlap. UTC-only Vercel and Cloudflare are unaffected.

Yes. Ten minutes is above GitHub Actions' five-minute floor and EventBridge's one-minute floor, although delayed starts can still occur on hosted platforms.

Use cron(0/10 * * * ? *). EventBridge uses six fields including year, requires ? in one day field, and wraps the expression in cron(...). Expression: 0/10 * * * ? *

Use 0 0/10 * * * ?. Quartz puts seconds first, so the leading 0 pins execution to second zero. Expression: 0 0/10 * * * ?

Use a durable cursor rather than a fixed 10-minute lookback. Cron does not replay downtime, while a small overlap plus deduplication protects against late-arriving records.

Plan for 144 baseline calls per day plus retries, and reserve rate-limit headroom for manual traffic. Crontap can run the HTTP schedule with retries when a call fails.

*/10 * * * *. Paste this into Linux crontab, Vercel cron, node-cron, robfig/cron, or a Kubernetes CronJob to run a job every 10 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.