Common Schedules
Every 2 hours
Regular sync or update. This page shows you how to implement this cron schedule with detailed examples and execution times.
12
Runs per day
10
Next executions
11
Expression length
Cron Expression
0 */2 * * *
Human Readable
Every 2 hours
Field Breakdown
| Field | Value | Meaning |
|---|---|---|
| Minute | 0 | When during the hour (0-59) |
| Hour | */2 | What hour of the day (0-23) |
| Day | * | What day of the month (1-31) |
| Month | * | What month (1-12) |
| Day of Week | * | What day of the week (0-7, 0=Sunday) |
Next 10 Execution Times
2026-07-28 10:00:00 UTC
2026-07-28 12:00:00 UTC
2026-07-28 14:00:00 UTC
2026-07-28 16:00:00 UTC
2026-07-28 18:00:00 UTC
2026-07-28 20:00:00 UTC
2026-07-28 22:00:00 UTC
2026-07-29 00:00:00 UTC
2026-07-29 02:00:00 UTC
2026-07-29 04:00:00 UTC
Note: Times shown in UTC. Adjust for your local timezone as needed.
Implementation Examples
Linux Crontab
0 */2 * * * /path/to/your/script.sh
Add this line to your crontab file using crontab -e
Docker Compose
services:
cron-job:
image: your-app:latest
command: |
sh -c 'echo "0 */2 * * * /app/script.sh" | crontab - && crond -f'
Kubernetes CronJob
apiVersion: batch/v1
kind: CronJob
metadata:
name: every-2-hours
spec:
schedule: "0 */2 * * *"
jobTemplate:
spec:
template:
spec:
containers:
- name: job
image: your-app:latest
command: ["/app/script.sh"]
restartPolicy: OnFailure
GitHub Actions
name: Every 2 hours
on:
schedule:
- cron: '0 */2 * * *'
jobs:
run:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Run task
run: ./script.sh
Common Use Cases
Regular sync or update
- • System maintenance and updates
- • Regular data synchronization
- • Automated reporting and notifications
- • Health checks and monitoring
Test This Expression
Use our free cron tools to test and validate this expression:
Learn More About Cron
Understand the syntax and patterns behind this expression:
More Common Schedules Examples
Every day at midnight
Daily backup or maintenance
0 0 * * *
Every weekday at 9 AM
Business hours notification
0 9 * * 1-5
Every 15 minutes
Frequent monitoring check
*/15 * * * *
Every Monday at 6:30 AM
Weekly report generation
30 6 * * 1
Every day at noon
Midday status check
0 12 * * *
Every day at 11:45 PM
Late night cleanup
45 23 * * *