Every 10 Minutes Cron – Free, Online, Private

The expression

*/10 * * * * is a five-field cron expression: minute, hour, day of month, month, day of week. There is no seconds field and no year field. Every 10 minutes, every hour, every day The next five run times on this page are computed in your browser with the same expression, in UTC, so a reload later in the hour shows a later list. Edit the box if you want to nudge a field and watch the list change, or open the line in the cron parser.

What each field is doing

The minute field is */10, a step of 10 across the whole 0–59 range. The matches are aligned to the start of that range. It does not mean "the value 10" and it does not start from the moment you save the file. The hour field is an asterisk, so every value in the 0–23 range is allowed. This field is not what limits the schedule. The day-of-month field is an asterisk, so every value in the 1–31 range is allowed. This field is not what limits the schedule. The month field is an asterisk, so every value in the 1–12 range is allowed. This field is not what limits the schedule. The day-of-week field is an asterisk, so every value in the 0–6, Sunday as 0 or 7 range is allowed. This field is not what limits the schedule.

When the day-of-month and day-of-week fields are both something other than *, many cron implementations run the job if either field matches. This preset leaves at least one of those two fields as *, so you do not have to resolve that rule to predict it. Names such as MON and JAN are readable and widely accepted. The snippets use numbers so a strict parser does not have to know the names.

Why this schedule

Ten minutes is a common compromise when five minutes would double the load and an hour would make the data feel stale. The expression is a step, so it is aligned to the hour. You get six runs an hour, not a run ten minutes after the previous one finished.

Importing a small feed, rotating a short-lived credential cache, and posting a digest of errors all sit comfortably on a ten-minute mark. A user-facing notification every ten minutes rarely does.

Where it goes wrong

If the job is still running at the next mark, cron starts another copy. There is no 'wait until idle' in the expression. GitHub-hosted runners can also delay a schedule past the mark and still report success. Check the timestamp in the log, not only the conclusion.

A sixth field is the seconds field used by Quartz, some Spring apps, and some Kubernetes setups that are not the classic CronJob schedule. Classic crontab, GitHub Actions, and the schedule field of a batch/v1 CronJob are five fields. If you paste a six-field line into those systems, the extra token shifts every field one place to the left and the job runs on a different day. L, W, and the # 'nth weekday' modifier are real in some daemons and rejected or reinterpreted in others. They are not used on this page. The English description and the next runs both refuse to guess at a token the calculator does not share with every target.

Crontab, GitHub Actions, and Kubernetes

GitHub Actions accepts this cadence. The schedule is UTC, it can start late when the service is busy, and it is dropped if the repository has had no activity for sixty days. The workflow file only needs the expression. It does not need a seconds field.

A user crontab does not include the username. A system crontab, the kind in /etc/crontab, inserts the user between the expression and the command. The line below is the user form. Kubernetes CronJob has used spec.timeZone since 1.27. The manifest sets it to Etc/UTC so the schedule matches the next-run list. Remove the field on a cluster older than that, and know that the schedule then uses the controller's zone.

crontab*/10 * * * * /usr/local/bin/job

GitHub Actionson:
  schedule:
    - cron: "*/10 * * * *"

Kubernetes CronJobapiVersion: batch/v1
kind: CronJob
metadata:
  name: every-10-minutes
spec:
  schedule: "*/10 * * * *"
  timeZone: "Etc/UTC"
  jobTemplate:
    spec:
      template:
        spec:
          containers:
            - name: job
              image: busybox:1.36
              args: ["echo", "every-10-minutes"]
          restartPolicy: OnFailure

• Keep the command idempotent. Cron does not remember a failure and it does not skip a run that is already in progress.
• Write the timezone next to the expression. UTC in the file and local time in the ticket are how a job fires eight hours early.
• Offset the minute if several jobs would otherwise start at once.