Cron: every 10 minutes
Six runs an hour, on the minutes that end in zero. */10 and 0-59/10 mean the same thing; so does the list 0,10,20,30,40,50.
Open in Cron Parser The expression is filled in: change it and watch the next runs.
Expression
*/10 * * * * Meaning
At every 10th minute: :00, :10, :20, :30, :40, :50
Next 5 runs
Your time zone
The same schedule on other platforms
| Platform | Written as | Note |
|---|---|---|
| Linux crontab | */10 * * * * | Five fields, in the server's local time zone. A % in the command has to be escaped as \%. |
| GitHub Actions | - cron: '*/10 * * * *' | Five fields, in UTC unless a timezone (an IANA name such as Europe/Warsaw) is set next to cron. Default branch only. The shortest interval is 5 minutes; when GitHub is busy, runs start late and some are dropped. |
| Kubernetes CronJob | schedule: "*/10 * * * *" | Five fields, in the controller's time zone unless spec.timeZone is set (Kubernetes 1.27 and later). concurrencyPolicy decides what happens when runs overlap. |
| systemd timer | OnCalendar=*:0/10 | Its own calendar syntax, in a .timer unit, local time. hourly, daily and monthly match cron, but weekly means Monday. Persistent=true catches up on runs missed while the machine was off. |
| AWS EventBridge | cron(0/10 * * * ? *) | Or rate(10 minutes), which counts from when the rule was created. |
| Quartz / Spring | 0 0/10 * * * ? | Six fields, seconds first. Quartz needs ? in one of the day fields and counts Sunday as 1; Spring accepts ? and numbers days like cron. |
Common mistakes
Offsetting it
A range before the step moves the start:
3-59/10runs at :03, :13, :23 and so on. Useful when several jobs share a server.Why not every 7 minutes?
A step that doesn't divide 60 restarts every hour.
*/7runs at :49 and :56, then at :00: a gap of 4 minutes, not 7. Pick 5, 6, 10, 12, 15, 20 or 30, or use a systemd timer withOnBootSec=1minandOnUnitActiveSec=7min.10 * * * *runs once an hourWithout the slash, 10 is a single minute: the job runs at :10 past each hour.