Cron every 2 hours: the expression, explained, in GitHub Actions

The cron expression for “every 2 hours” is 0 */2 * * *. This page shows what each field does, the next five times it will fire, the mistake most people make with it, and a working GitHub Actions example you can paste.

The expression

0 */2 * * *

Field	Value	Meaning
minute	0	exactly 0
hour	*/2	every 2 hours, starting at 0
day of month	*	every day of month
month	*	every month
day of week	*	every day of week

Next five runs (UTC, from now)

2026-09-18 00:00 UTC
2026-09-18 02:00 UTC
2026-09-18 04:00 UTC
2026-09-18 06:00 UTC
2026-09-18 08:00 UTC

Mistakes people make with this schedule

Using "* */2 * * *" for every 2 hours. That runs every minute of every 2th hour. The minute field must be the fixed number 0.
Assuming the server clock is your clock. Cron runs in the machine’s timezone unless the runtime says otherwise; the examples here are UTC.
No lock around a job that might overlap itself, and no alert when it silently stops. That second one is what Supercrontab is for.

Run it in your stack

Linux crontab Laravel WordPress Next.js / Vercel Node.js Python Docker GitHub Actions

# .github/workflows/cron.yml
on:
  schedule:
    - cron: '0 */2 * * *'
jobs:
  run:
    runs-on: ubuntu-latest
    steps:
      - run: curl -fsS https://example.com/cron/run

Scheduled workflows can be delayed by many minutes at busy hours, and are disabled after 60 days of repo inactivity.

Questions

Does 0 */2 * * * run in my local time?

Only if the scheduler is configured for it. crontab uses the system timezone; Vercel and GitHub Actions always use UTC; Laravel and node-cron take a timezone option. In Supercrontab the timezone is a field on the job.

What if the previous run is still going?

Classic cron starts the next run anyway. Add a lock (flock on Linux, withoutOverlapping() in Laravel) or let Supercrontab skip the tick while the previous request is open.

Is there a shorter way to write this?

No. The five-field form is the shortest portable version.