Cron Expression for Every 5 Minutes (*/5 * * * *)

Pre-configured cron expression */5 * * * * to run a job every 5 minutes in Linux crontab, GitHub Actions, Kubernetes CronJobs, and Vercel/AWS EventBridge.

*/5 * * * *
"Every 5 minutes"

How the */5 * * * * Cron Schedule Runs Every 5 Minutes

In standard 5-field POSIX crontab syntax (Minute Hour Day-of-Month Month Day-of-Week), the step expression */5 * * * * instructs the cron daemon to trigger at every minute divisible by 5 across every hour of every day: :00, :05, :10, :15, :20, :25, :30, :35, :40, :45, :50, and :55 (288 executions per 24-hour day).

Because */5 is anchored to clock boundaries rather than process startup time, all distributed workers running */5 * * * * fire simultaneously on the 5-minute mark. When scheduling high-frequency health checks, queue pollers, or metrics scrapers in Linux crontab, Kubernetes CronJob manifests (concurrencyPolicy: Forbid), or GitHub Actions schedule workflows, prevent overlapping runs with flock(1) or concurrency guards.

  • Field 1 — Minute (*/5): Step value /5 over wildcard * fires when minute mod 5 === 0 (0, 5, 10, ..., 55).
  • Fields 2–5 — Hour, Day, Month, Weekday (* * * *): Wildcard * in the remaining four fields means every hour (0–23), every calendar day (1–31), every month (1–12), and every day of the week (0–6).
  • Preventing Overlapping 5-Minute Jobs: Wrap crontab commands with /usr/bin/flock -n /tmp/job.lock or set concurrencyPolicy: Forbid in Kubernetes CronJob specs.

Platform Examples: Linux Crontab, Kubernetes CronJob & GitHub Actions

When deploying */5 * * * * across cloud and container schedulers, be aware of platform-specific minimum interval quotas and timezone rules. In Linux /etc/crontab or user crontab -e files, always use absolute binary paths (such as /usr/bin/curl or /usr/local/bin/node) because cron executes with a minimal PATH=/usr/bin:/bin environment.

In GitHub Actions (on.schedule), */5 * * * * is the shortest supported cron interval, though workflow runs may experience a 3-to-10-minute queue delay during peak UTC hours. In Kubernetes CronJob resources, pair schedule: "*/5 * * * *" with startingDeadlineSeconds: 120 and successfulJobsHistoryLimit: 3 so stalled pods do not accumulate in the cluster namespace.

  • Linux Crontab Entry with Non-Blocking Lock: */5 * * * * /usr/bin/flock -n /var/lock/sync.lock /usr/local/bin/sync-worker.sh >> /var/log/sync.log 2>&1
  • Staggered Step Offset (2-59/5 * * * *): Shifts execution off the top of the hour (:02, :07, :12, ..., :57) to avoid colliding with hourly and daily cron jobs at :00.

Practical Real-World Use Cases

A 5-minute cron cadence balances near-real-time freshness against API rate limits and serverless invocation quotas:

  • Transactional Outbox & Webhook Retry Sweeps: Poll unacknowledged rows in a PostgreSQL outbox table every 5 minutes to replay transient HTTP 502/504 webhook deliveries with exponential backoff.
  • Synthetic Uptime Probes & TLS Expiry Monitors: Schedule lightweight Kubernetes CronJobs or GitHub Actions checks every 5 minutes to verify external health endpoints and alert PagerDuty/Slack on degradation.
  • Materialized View Refreshes & Cache Warmers: Run REFRESH MATERIALIZED VIEW CONCURRENTLY on dashboard KPI rollups every 5 minutes so read traffic hits pre-aggregated indexes instead of raw event tables.

Frequently Asked Questions

What is the exact cron expression for every 5 minutes?

The standard 5-field cron expression for every 5 minutes is */5 * * * *, which executes at minute 0, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, and 55 of every hour.

How do I stagger a 5-minute cron job so it does not spike at :00 and :05?

Use an offset range with a step value such as 2-59/5 * * * *, which runs every 5 minutes starting at minute :02 (:02, :07, :12, ..., :57) instead of :00.