Cron Every 10 Minutes
Every 10 minutes is */10 in the minute field: six runs an hour, at :00, :10, :20, :30, :40 and :50.
minute · hour · day · month · weekday
Build it with controlsEvery 10 min
The last hour counts in full: the last run each day is at 11:50 PM.
In plain English
Every 10 minutes.
Tap a field to see what it means.
- Next run
- —
- Usually every
- —
- Time zone
- Yours
Convert to another schedulerQuartz, Spring, AWS, GitHub Actions, Kubernetes
| Standard cron | */10 * * * * | current |
|---|---|---|
| Quartz | 0 0/10 * * * ? | |
| Spring | 0 */10 * * * * | |
| AWS EventBridge | cron(0/10 * * * ? *) | |
| GitHub Actions | */10 * * * * | |
| Kubernetes | */10 * * * * |
About Standard cronTime zone, day numbering, daylight saving
- Runs in the machine’s local time zone; cronie also reads CRON_TZ at the top of the crontab.
- Five fields, then the command. Day of week is 0–7 (0 and 7 are Sunday) or SUN–SAT; months 1–12 or JAN–DEC.
- When both day fields are set, a day that matches either one runs.
- Daylight saving: a job at a fixed time in a skipped hour runs right after the change, and one in a repeated hour runs once. Jobs with * in the minute or hour follow the clock.
Sources: crontab(5), cronie, cron(8), cronie, POSIX crontab.
How this works: Method, 10 sources,
How this works
Method
The expression is read field by field with the rules of the scheduler you pick (ranges, lists, steps, names, @ macros, and L, W and # where it has them) into the values each field allows. The next runs come from stepping forward through the calendar in the chosen time zone, day by day and then time by time, using that scheduler’s rule for when both day fields are set and its documented rule for daylight saving (where it has none, a skipped time is skipped and a repeated one runs once). A conversion to another scheduler is parsed back and checked against the original before it is shown.
Sources
Changes
- First version: plain English and the next runs for six schedulers, a builder, conversion between them, and 20 pages for common schedules.
Worked example: */10 * * * *
Say the clock reads Monday 4 January 2027, 10:03 AM UTC. */10 * * * * means “every 10 minutes”, so the next five runs are Monday 4 January 2027, 10:10 AM, 10:20 AM, 10:30 AM, 10:40 AM and 10:50 AM.
In UTC, where no clock change interrupts it, that comes to 144 runs a day, 1,008 a week and 52,560 in 2027.
Ten-minute steps
*/10 in the minute field matches minutes 0, 10, 20, 30, 40 and 50. With every other field left as *, the job runs six times an hour, 144 times a day, on the clock’s ten-minute marks.
The same set can be written as a list, 0,10,20,30,40,50, or as a range with a step, 0-59/10. All three mean exactly the same to cron; the step form is just shorter.
If many jobs on one machine use */10, they all start in the same second. Offsetting some of them, 3-59/10 for :03, :13, :23 and so on, spreads the load while keeping the ten-minute rhythm.
Pitfalls
- A step that doesn’t divide 60, such as */7, gives an uneven last gap: :56 is followed by :00, four minutes later, because the count restarts each hour.
- In Quartz the minute is the second field: 0 0/10 * * * ? (seconds, then minutes). Putting 0/10 first would run every ten seconds.
- Long runs: if a run can take more than ten minutes, the next one starts anyway. Use a lock (flock on Linux, concurrencyPolicy in Kubernetes).
- Steps are evaluated only within their own field: */23 in the hour field means hour 0 and hour 23, not every 23 hours. Source: crontab(5), cronie.
- In Quartz the fields are second, minute, hour, day of month, month, day of week and an optional year. Source: Quartz CronExpression.
“Every 10 Minutes” in every scheduler
The same schedule written for each scheduler, converted and checked by this tool. A dash means that scheduler can’t express it in one expression; the note says why.
| Scheduler | Expression | Note |
|---|---|---|
| Standard Unix cron (Vixie cron, cronie) | */10 * * * * | |
| Quartz Scheduler (Java) | 0 0/10 * * * ? | |
| Spring Framework @Scheduled | 0 */10 * * * * | |
| Amazon EventBridge cron() | cron(0/10 * * * ? *) | |
| GitHub Actions schedule | */10 * * * * | |
| Kubernetes CronJob | */10 * * * * |
Frequently Asked Questions
Is */10 the same as 0,10,20,30,40,50?
Yes. A step expands to a list of values when the crontab is read, so both lines produce identical runs.
How do I run every 10 minutes starting at 5 past?
Give the step a range that starts at 5: 5-59/10 runs at :05, :15, :25, :35, :45 and :55.
What is every 10 minutes in AWS EventBridge?
cron(0/10 * * * ? *): minutes first, a ? in the day-of-week field, and * for the year. AWS also accepts rate(10 minutes), which counts from when the schedule was created rather than from the clock.