Cron Expression for Every Hour on the Hour (0 * * * *)

Pre-configured hourly cron expression 0 * * * * (or @hourly). Runs once per hour at minute :00 across Linux crontab, GitHub Actions, and cloud schedulers.

0 * * * *
"Every hour"

Why Hourly Cron Jobs Use 0 * * * * (Not * */1 * * *)

The canonical cron expression to run a job once every hour at the top of the hour is 0 * * * * (equivalent to the @hourly shorthand in Vixie cron and systemd-cron). Setting the first field (Minute) to 0 ensures the job triggers only when the clock minute equals :00 (00:00, 01:00, 02:00, ..., 23:00 — 24 times per day).

A frequent bug in production crontabs is writing * */1 * * * thinking it means "every 1 hour." Because the first field is *, * */1 * * * actually runs every single minute of every hour (1,440 times per day). Always pin the minute field to a specific integer (0 for top of the hour, or 15 for quarter past the hour: 15 * * * *) when scheduling hourly tasks.

  • Top of the Hour (0 * * * *): Fires at 00:00, 01:00, 02:00, ..., 23:00 UTC/local server time.
  • Staggered Hourly Window (e.g., 17 * * * *): Runs once per hour at 17 minutes past the hour to avoid thundering-herd database load at :00.

Business-Hours & Weekday-Only Hourly Cron Variations (0 9-17 * * 1-5)

While 0 * * * * runs 24 hours a day across all 7 days of the week (168 runs per week), many enterprise ETL pipelines, Slack/email digest notifications, and cache warmers only need to run during active business hours or every N hours. You can restrict the Hour (field 2) and Day-of-Week (field 5) directly from this preset.

For example, 0 9-17 * * 1-5 triggers on the hour from 09:00 AM through 05:00 PM Monday through Friday, whereas 0 */2 * * * triggers once every 2 hours on even hours (00:00, 02:00, 04:00, ..., 22:00).

  • Weekday Business Hours Only (0 9-17 * * 1-5): Fires at :00 from 9 AM to 5 PM Monday–Friday, skipping nights and weekends to save cloud compute costs.
  • Every 2, 4, or 6 Hours (0 */2 * * * / 0 */6 * * *): Combine minute 0 with an hour step value (/2, /4, /6) for multi-hour synchronization intervals.

Practical Real-World Use Cases

Hourly cron schedules (0 * * * *) power recurring operational batch jobs that do not require sub-hour polling:

  • Incremental CRM, Stripe & ERP Data Warehouse Syncs: Pull updated invoices, subscriptions, and support tickets once per hour into BigQuery, Snowflake, or ClickHouse staging tables.
  • OAuth Token Rotation & Ephemeral Temp Cleanup: Refresh short-lived cloud IAM/OIDC credentials and purge stale upload staging chunks older than 60 minutes.
  • Search Sitemap & RSS Feed Regeneration: Rebuild XML sitemaps, product inventory feeds (Google Merchant Center), and hourly currency exchange rate caches.

Frequently Asked Questions

Why does * */1 * * * run every minute instead of every hour?

In cron syntax, the first field controls the minute. Leaving the first field as * tells cron to match every minute (0 through 59) of every hour. To run once per hour, set the minute field to 0: 0 * * * *.

Is @hourly identical to 0 * * * * in Linux crontab?

Yes, in Vixie cron (Ubuntu/Debian/RHEL) and FreeBSD cron, @hourly is a built-in macro that expands directly to 0 * * * *. However, cloud schedulers like GitHub Actions and Kubernetes CronJobs require the explicit 5-field 0 * * * * format.