Field-by-field breakdown
| Field | Value | Meaning |
|---|---|---|
| Minute | */30 | 0 and 30 |
| Hour | * | Every hour |
| Day of month | * | Every day of the month |
| Month | * | Every month |
| Day of week | * | Every day of the week |
Copy-paste examples
Linux crontab
# crontab -e
*/30 * * * * /usr/local/bin/my-job.sh >> /var/log/my-job.log 2>&1Kubernetes CronJob
apiVersion: batch/v1
kind: CronJob
metadata:
name: my-job
spec:
schedule: "*/30 * * * *"
concurrencyPolicy: Forbid
jobTemplate:
spec:
template:
spec:
restartPolicy: OnFailure
containers:
- name: my-job
image: busybox:1.36
command: ["sh", "-c", "date; echo Hello from cron"]GitHub Actions
on:
schedule:
- cron: '*/30 * * * *' # always UTCGitHub Actions evaluates schedules in UTC, does not accept macros such as @daily, and will not run workflows more often than every 5 minutes; runs can also be delayed during periods of high load.
Common variations
Click an expression to load it into the tool above.
| Cron expression | Schedule |
|---|---|
| At minutes 0 and 30 past the hour, between 9:00 AM and 5:59 PM, Monday through Friday. | |
| At minutes 15 and 45 past the hour. | |
| Every 30 minutes, Monday through Friday. | |
| At minutes 0 and 30 past the hour. |
Frequently asked questions
What does */30 * * * * mean in cron?
Every 30 minutes. The five fields are minute */30, hour *, day of month *, month * and day of week *.
How do I run a cron job every 30 minutes in Linux?
Run crontab -e, add the line */30 * * * * /path/to/command, then save and exit. Use absolute paths, redirect output to a log file, and confirm it runs with grep CRON /var/log/syslog.
When will */30 * * * * run next?
It depends on the current time and the time zone of the machine running cron. The calculator on this page shows the next 5 run times in your local time zone; on a server, cron uses the system time zone, which is often UTC.