What each field means
| Field | Position | Meaning |
|---|---|---|
*/2 | minute | every 2nd minute (0, 2, 4, 6, …) |
* | hour | every hour |
* | day of month | every day of month |
* | month | every month |
* | day of week | every day of week |
Example run times
Starting from Wednesday 07 Jan 2026, 10:17, the next runs are:
- Wed 07 Jan 2026, 10:18
- Wed 07 Jan 2026, 10:20
- Wed 07 Jan 2026, 10:22
- Wed 07 Jan 2026, 10:24
- Wed 07 Jan 2026, 10:26
- Wed 07 Jan 2026, 10:28
How often it runs
- 720 runs on each day it is active.
- Active on 365 of the 365 days in 2026, for 262,800 runs that year.
- Runs are always exactly 2 minutes apart.
Use it on your platform
Linux crontab
*/2 * * * * /path/to/command
Edit with crontab -e. Cron uses the server's local time zone.
GitHub Actions
on:
schedule:
- cron: '*/2 * * * *'
Schedules are evaluated in UTC, and runs can start late when GitHub is busy.
GitHub Actions runs scheduled workflows at most once every 5 minutes, so this schedule will not run as often there as it does in crontab.
Kubernetes CronJob
apiVersion: batch/v1
kind: CronJob
metadata:
name: my-job
spec:
schedule: "*/2 * * * *"
timeZone: "Etc/UTC"
jobTemplate:
spec:
template:
spec:
containers:
- name: my-job
image: busybox
command: ["sh", "-c", "date"]
restartPolicy: OnFailure
Without timeZone, the schedule follows the time zone of the kube-controller-manager.
AWS EventBridge
cron(0/2 * * * ? *)
AWS uses six fields (the last is the year), needs ? in either day-of-month or
day-of-week, and counts weekdays from 1 = Sunday, so names like MON are safer than numbers.
EventBridge rules run in UTC; EventBridge Scheduler lets you choose a time zone.
Spring @Scheduled
@Scheduled(cron = "0 */2 * * * *")
Spring adds a seconds field at the start, so prepend 0 to run at second zero.
Quartz
0 0/2 * * * ?
Quartz also starts with seconds and, like AWS, requires ? in one of the day fields.