*/10 * * * * Open in Cron Expression Parser Field by field
| Field | Value | Matches |
|---|---|---|
| Minute | */10 | 0, 10, 20, 30, 40, 50 |
| Hour | * | Every value |
| Day of month | * | Every value |
| Month | * | Every value |
| Day of week | * | Every value |
Next run times
Example: the first 6 runs after January 1, 2026 (UTC).
- Thu, Jan 1, 2026, 00:10
- Thu, Jan 1, 2026, 00:20
- Thu, Jan 1, 2026, 00:30
- Thu, Jan 1, 2026, 00:40
- Thu, Jan 1, 2026, 00:50
- Thu, Jan 1, 2026, 01:00
Ready-to-use versions
*/10 * * * * /path/to/command Add the line with crontab -e. It runs in the server's time zone unless CRON_TZ or TZ is set.
apiVersion: batch/v1
kind: CronJob
metadata:
name: every-10-minutes
spec:
schedule: "*/10 * * * *"
timeZone: "Etc/UTC"
concurrencyPolicy: Forbid
jobTemplate:
spec:
template:
spec:
restartPolicy: OnFailure
containers:
- name: job
image: busybox:1.36
command: ["/bin/sh", "-c", "date; echo run"] Set spec.timeZone (Kubernetes 1.27+); without it the schedule follows the controller manager's time zone, usually UTC.
on:
schedule:
- cron: '*/10 * * * *'
workflow_dispatch: GitHub Actions always uses UTC, accepts intervals of 5 minutes or more, and may start scheduled runs late under load.
0 */10 * * * ? Quartz puts seconds first and needs ? in either day-of-month or day-of-week. Days are 1–7 from Sunday, so names are safer.
@Scheduled(cron = "0 */10 * * * *") Spring @Scheduled(cron = …) takes six fields: seconds, then the usual five.
FAQ
› How can I offset a 10-minute job so it does not run on the hour?
Start the step from another minute, for example 3-59/10 * * * * runs at 03, 13, 23, 33, 43 and 53.
› Which time zone does */10 * * * * run in?
Cron uses the time zone of the machine or service that runs it. On Linux that is the system time zone unless CRON_TZ or TZ is set; Kubernetes CronJobs accept spec.timeZone; GitHub Actions always uses UTC.
› How can I check this schedule before deploying it?
Open */10 * * * * in the Cron Expression Parser on this site. It explains each field and lists the upcoming runs in your local time or UTC, right in your browser.