Cron expression generator · every 10 minutes

Cron job every 10 minutes

The crontab line for a job every 10 minutes is */10 * * * *. It runs 144 times a day, 52,560 times a year. Edit it below to see the next runs in your time zone.

—

Next runs

    Field by field

    How */10 * * * * reads

    The five fields are minute, hour, day of month, month and day of week. A star means every value.

    FieldValueMeaning
    Minute*/10every 10th minute: 0, 10, 20, 30, 40, 50
    Hour*every hour
    Day of month*every day of month
    Month*every month
    Day of week*every day of week

    For example, from Wednesday 6 January 2027 at 10:07 the next runs are: Wed 6 Jan 2027, 10:10; Wed 6 Jan 2027, 10:20; Wed 6 Jan 2027, 10:30; Wed 6 Jan 2027, 10:40; Wed 6 Jan 2027, 10:50.

    When to use it

    What a job every 10 minutes is for

    Every 10 minutes fits jobs that cost a little more each run: importing orders from a marketplace, generating thumbnails in batches, or pulling statistics from an API with a rate limit.

    Mistakes

    Common mistakes

    • «*/10» in the hour field («0 */10 * * *») means hours 0, 10 and 20, not every 10 minutes.
    • «0,10,20,30,40,50 * * * *» is the same schedule written out; both forms are standard and either is fine.
    systemd

    The same schedule as a systemd timer

    On systems with systemd, a timer can replace the crontab line: OnCalendar=*:0/10. Check it with systemd-analyze calendar "*:0/10", which prints the next run.

    Monitoring

    Know when it didn’t run

    Cron doesn’t tell you when a job stops running. A heartbeat monitor alerts you when the job’s ping is late. Heartbeat periods go 5 and 15 minutes, with no 10, so for this job choose 5 minutes with a grace time of 5 minutes or more: a missed run is then noticed within about 10 minutes.

    What is the cron expression for a job every 10 minutes?

    */10 * * * *. It runs 144 times a day, 52,560 times a year, on the server’s clock.

    How do I run a job every 10 minutes with systemd instead?

    Create a timer with OnCalendar=*:0/10 next to a service that runs the job, then enable it with systemctl enable --now name.timer. Persistent=true also runs a run that was missed while the machine was off.