Cron Job Every 2 hours

Run a job every two hours on the even hours. Use the cron string 0 */2 * * *, see the next 5 execution times, and copy Python, Node.js, Bash and n8n snippets.

Quick Answers

What does the "Every 2 hours" cron expression mean?
This cron expression is "0 */2 * * *", which in plain English means: Run a job every two hours on the even hours..
When will this cron expression run next?
With the expression "0 */2 * * *", the next execution times are Fri, Aug 14, 2026, 02:00:00 PM UTC, Fri, Aug 14, 2026, 04:00:00 PM UTC, Fri, Aug 14, 2026, 06:00:00 PM UTC.
How do I use this cron expression?
Copy the exact string into crontab, cron triggers, or any scheduler such as GitHub Actions, n8n or Docker. Pre-built code snippets for Python, Node.js, Bash, Docker, GitHub Actions and n8n are included on this page.
Explore the full Cron Cheat Sheet with all 50 schedules
Cron Expression
Copy this exact string into crontab, cron triggers, or schedulers.
0 */2 * * *

Human readable

Run a job every two hours on the even hours.

Next 5 execution times

  1. 1Fri, Aug 14, 2026, 02:00:00 PM UTC
  2. 2Fri, Aug 14, 2026, 04:00:00 PM UTC
  3. 3Fri, Aug 14, 2026, 06:00:00 PM UTC
  4. 4Fri, Aug 14, 2026, 08:00:00 PM UTC
  5. 5Fri, Aug 14, 2026, 10:00:00 PM UTC
Python
from crontab import CronTab
from datetime import datetime

# Install: pip install python-crontab
cron = CronTab(user=True)
job = cron.new(command="/usr/bin/python3 /var/www/job_every-2-hours.py", comment="scheduled by crongen")
job.setall("0 */2 * * *")
cron.write()

print(f"Installed: 0 */2 * * * -> /usr/bin/python3 /var/www/job_every-2-hours.py")

Related schedules

Every minute

* * * * *

Every 2 minutes

*/2 * * * *

Every 5 minutes

*/5 * * * *

Every 10 minutes

*/10 * * * *

Every 15 minutes

*/15 * * * *

Every 20 minutes

*/20 * * * *

About the "every 2 hours" cron schedule

The "every 2 hours" cron schedule uses the expression "0 */2 * * *". This schedule fires 12 times per day.

In plain English the cron string "0 */2 * * *" means: On the hour, every 2 hours.

This cadence is a common choice for long-running build or maintenance pipelines that tolerate multi-hour gaps and aggregating logs or telemetry into batched reports. The schedule is deliberately kept simple: copy the string into any cron-aware scheduler (crontab, Vercel Cron, GitHub Actions, n8n, Docker or Kubernetes CronJob) and the run will repeat automatically — steady, with no manual triggering.

Frequently asked questions