Xerobit

Cron Every 6 Hours: 0 */6 * * *

The cron expression for every 6 hours is 0 */6 * * *. It runs 4 times per day, and the table below explains every field.

  • Cron expression
    0 */6 * * *
  • Schedule
    every 6 hours
  • Runs per day
    4
  • Runs per 30 days
    120
  • systemd OnCalendar
    *-*-* 0/6:00:00
  • AWS EventBridge
    cron(0 0/6 * * ? *)

What 0 */6 * * * means

FieldValueMeaning
Minute0at minute 0
Hour*/6every 6th hour, starting at hour 0
Day of month*every day
Month*every month
Day of week*every day of the week

The five fields of a standard cron expression are, in order: minute, hour, day of month, month and day of week.

When every 6 hours runs

The first run times in a day are: 00:00, 06:00, 12:00, 18:00. Over time that is 4 per day, 28 per week, about 120 per 30 days and 1,460 per year.

Copy-ready syntax for every 6 hours

crontab

0 */6 * * * /path/to/script.sh >> /var/log/job.log 2>&1

GitHub Actions

on:
  schedule:
    - cron: '0 */6 * * *'

GitHub Actions runs scheduled workflows in UTC and may start them a few minutes late when GitHub is busy.

Kubernetes CronJob

apiVersion: batch/v1
kind: CronJob
spec:
  schedule: "0 */6 * * *"
  concurrencyPolicy: Forbid

Setting concurrencyPolicy: Forbid stops a new run from starting while the previous one is still going.

systemd timer

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

AWS EventBridge

cron(0 0/6 * * ? *)

EventBridge cron has six fields and needs a ? in either the day-of-month or the day-of-week field. The simpler rate(6 hours) form works for fixed intervals.

When to use every 6 hours

Automated security audits scan file integrity and permission changes every six hours across production servers. Large scale data exports to partner organizations also use this schedule to deliver updated datasets throughout the day.

What can go wrong

If an export job fails silently, up to six hours of data changes go undelivered before the next attempt. Detecting these gaps requires separate monitoring since the cron daemon only verifies execution, not success.

Cron uses the time zone of the machine or service running it, so check whether that is UTC or local time before you rely on the clock times above.

Other common schedules

FAQ

What is the cron expression for every 6 hours?

Use 0 */6 * * *. It is the standard five-field form accepted by Linux crontab, Kubernetes CronJobs and GitHub Actions.

How many times a day does 0 */6 * * * run?

4 times per day, or 120 over 30 days.

How do I test a cron expression?

Build it in the cron builder, which explains each field in plain English and lists the next run times.

More cron