Every Hour Cron Expression — 0 * * * *
Cron Expression
0 * * * *What it means
Runs at the start of every hour
A go-to schedule for hourly summaries, token rotation, and snapshot backups. The 0 in the minute field ensures it runs exactly on the hour, every hour.
Next 8 Scheduled Runs (UTC)
- 1.Wed, 24 Jun 2026 19:00:00 GMT
- 2.Wed, 24 Jun 2026 20:00:00 GMT
- 3.Wed, 24 Jun 2026 21:00:00 GMT
- 4.Wed, 24 Jun 2026 22:00:00 GMT
- 5.Wed, 24 Jun 2026 23:00:00 GMT
- 6.Thu, 25 Jun 2026 00:00:00 GMT
- 7.Thu, 25 Jun 2026 01:00:00 GMT
- 8.Thu, 25 Jun 2026 02:00:00 GMT
Platform Snippets
GitHub Actions
- cron: '0 * * * *'
Kubernetes CronJob
schedule: "0 * * * *"
AWS EventBridge
cron(0 * * * ? *)
AWS uses a 6-field format with year and requires either DOM or DOW to be ?.
systemd Timer
[Timer] OnCalendar=*-*-* *:00:00 Persistent=true
Want to decode a different expression or test your own?
Test this expression interactively →FAQ
What does the cron expression 0 * * * * mean?
Runs at the start of every hour. A go-to schedule for hourly summaries, token rotation, and snapshot backups. The 0 in the minute field ensures it runs exactly on the hour, every hour.
How do I use 0 * * * * in GitHub Actions?
Add a schedule trigger under the "on" key in your workflow YAML: on: schedule: - cron: '0 * * * *'. This will run your workflow runs at the start of every hour. Note that GitHub Actions uses UTC time.
Is the cron expression 0 * * * * valid for Kubernetes CronJobs?
Yes. Set the schedule field in your CronJob spec to "0 * * * *". Kubernetes CronJobs use standard 5-field cron syntax and run in UTC by default unless you configure a timeZone field.