Cron every 10 minutes
*/10 * * * * — Minute 0, 10, 20, 30, 40 and 50 of every hour: six runs an hour, 144 a day. Ten divides sixty evenly, so the gap is always exactly ten minutes.
Runs
Try one
The same schedule in every dialect
| Where | Expression | |
|---|---|---|
| Linux / Unix crontab, Kubernetes, GitHub Actions | */10 * * * * | explain |
| Quartz Scheduler | 0 0/10 * ? * * | explain |
| AWS EventBridge | cron(0/10 * * * ? *) rate(10 minutes) | explain |
Spring @Scheduled | 0 */10 * * * * | explain |
| Jenkins | H/10 * * * * | H calculator |
systemd timer OnCalendar= | *-*-* *:00/10:00 | test |
AWS rate(10 minutes) repeats at a fixed interval from when the rule or schedule was created, so it is not aligned to the clock the way the cron() form is.
Things to know
- The same pattern with a start offset,
3-59/10 * * * *, runs at :03, :13, :23 … — handy when several ten-minute jobs share a machine. - Steps restart at the top of every hour. That is harmless for 10 (it divides 60) but
*/7would leave a 4-minute gap after :56.
Variations
| Expression | Runs |
|---|---|
| */10 8-20 * * * | every 10 minutes from 08:00 to 20:59 |
| 3-59/10 * * * * | every 10 minutes at :03, :13, :23 … |
| */10 * * * 1-5 | every 10 minutes on weekdays |
How to use this schedule
- Open your crontab with
crontab -e(or the scheduler's config file). - Add a line with the expression followed by the command:
*/10 * * * * /usr/local/bin/job.sh. Use absolute paths — cron runs with a minimalPATH. - Save. cron picks the change up automatically; check the next run times above, in the time zone your server uses.
- Redirect output if you want to keep it: append
>> /var/log/job.log 2>&1. The crontab line builder assembles the whole line.
FAQ
Is "*/10 * * * *" the same on every server?
The five-field form means the same thing in Linux cron, Kubernetes, GitHub Actions and most libraries. The clock it follows differs:
a Linux server uses its own time zone (or CRON_TZ on cronie), GitHub Actions and AWS EventBridge rules use UTC unless a time zone is configured, and Kubernetes uses the controller's zone unless .spec.timeZone is set.
Why do Quartz and AWS need a "?"
Both require exactly one of day-of-month and day-of-week to be ?, meaning "no specific value"; they refuse an expression that restricts both, or leaves both as *.
How do I check it will run when I expect?
The widget above lists the next runs in the time zone you choose, and flags any run that lands in a daylight-saving gap or a repeated hour. For a whole crontab, paste it into the crontab viewer.