Cron expression for every 10 minutes

Free

*/10 * * * * - Every 10 minutes.

Field by field

*/10 * * * * reads: Every 10 minutes. That is 144 runs a day.

What each field of */10 * * * * selects
FieldValueSelects
Minute*/10every 10 minutes: 0, 10, 20, 30, 40 and 50
Hour*every hour
Day of month*any day of the month
Month*every month
Day of week*any day of the week

Worth knowing

  • 144 runs a day, at minutes 0, 10, 20, 30, 40 and 50 of every hour.
  • A step divides the field's range from its start, so */10 never produces :05 - use 5-59/10 for :05, :15, :25…

Variations

  • 5-59/10 * * * *Every 10 minutes at :05, :15, :25…Explain it
  • */10 8-20 * * *Every 10 minutes between 08:00 and 20:50Explain it

The same schedule elsewhere

crontab

*/10 * * * * /path/to/job.sh

Runs in the machine's local timezone. crontab -e to edit.

GitHub Actions

on:
  schedule:
    - cron: "*/10 * * * *"

Always UTC. Nothing more often than every 5 minutes, and runs can start late when GitHub is busy.

Kubernetes CronJob

spec:
  schedule: "*/10 * * * *"
  timeZone: "Asia/Kolkata"

timeZone needs Kubernetes 1.27 or later; without it the controller's zone applies, usually UTC.

Spring @Scheduled

@Scheduled(cron = "0 */10 * * * *")

Six fields: seconds come first. Days are written as names, which Spring and cron read alike.

Quartz

0 0/10 * * * ?

One of day-of-month and day-of-week must be ?. Quartz counts days 1-7 from Sunday, so names are safer than numbers.

AWS EventBridge

cron(0/10 * * * ? *)

Six fields, the last one the year. UTC unless the schedule sets a timezone. Days count from Sunday, as in Quartz.

systemd timer

[Timer]
OnCalendar=*-*-* *:00/10:00
Persistent=true

Persistent=true runs a job that was missed while the machine was off, once it is back.