Taprico

Cron Expression for Every Minute (* * * * *)

Schedule summary: Every 1 minute (60 times/hour). Test live US Eastern, Pacific, and UTC execution timestamps below or copy platform-ready configs.

Presets:
Human-Readable Schedule

"Every minute, every hour, every day"

Minute0–59
Hour0–23
Day (Month)1–31
Month1–12
Weekday0–6 (Sun=0)

Next 10 Scheduled Executions

America/New_York
  1. 1Tue, Nov 17, 2026, 09:01 AM EST
  2. 2Tue, Nov 17, 2026, 09:02 AM EST
  3. 3Tue, Nov 17, 2026, 09:03 AM EST
  4. 4Tue, Nov 17, 2026, 09:04 AM EST
  5. 5Tue, Nov 17, 2026, 09:05 AM EST
  6. 6Tue, Nov 17, 2026, 09:06 AM EST
  7. 7Tue, Nov 17, 2026, 09:07 AM EST
  8. 8Tue, Nov 17, 2026, 09:08 AM EST
  9. 9Tue, Nov 17, 2026, 09:09 AM EST
  10. 10Tue, Nov 17, 2026, 09:10 AM EST

Cron Operator Reference

*Any / every value in this field
,Value list separator (e.g., 1,15 runs on 1st & 15th)
-Inclusive range (e.g., 9-17 means 9 AM through 5 PM)
/Step increment (e.g., */10 runs every 10 units)
1-5Monday through Friday in Weekday field

Copy-Ready Snippets for Linux, GitHub Actions, Kubernetes & AWS

Linux / POSIX Crontab
* * * * * /usr/local/bin/run-task.sh >> /var/log/task.log 2>&1
GitHub Actions Workflow (YAML)
on:
  schedule:
    - cron: '* * * * *' # Runs in UTC
Kubernetes CronJob Spec (With US Eastern TZ)
apiVersion: batch/v1
kind: CronJob
spec:
  schedule: "* * * * *"
  timeZone: "America/New_York"
AWS EventBridge / CloudWatch (6-Field Syntax)
cron(* * * * ? *)

Production Use Cases & Gotchas

  • Local worker queue polling and heartbeat health checks.
  • Lightweight metrics scraping when sub-minute systemd timers are unavailable.
  • Short-lived cache invalidation or webhook retry sweeps.

Production Note: Always wrap 1-minute jobs with flock or a distributed lock. Note that GitHub Actions enforces a 5-minute minimum interval on schedule triggers.

Frequently Asked Questions

How do you write a cron expression for every 1 minute (60 times/hour)? +

Use the 5-field POSIX cron expression "* * * * *" for Linux crontab, Kubernetes CronJobs, and GitHub Actions. In AWS EventBridge (6-field format), use "cron(* * * * ? *)".

What timezone does * * * * * run in on GitHub Actions and AWS? +

GitHub Actions and AWS EventBridge evaluate "* * * * *" strictly in UTC (Coordinated Universal Time). Kubernetes v1.27+ allows setting spec.timeZone (such as "America/New_York").

What is the biggest gotcha with "* * * * *" in production? +

Always wrap 1-minute jobs with flock or a distributed lock. Note that GitHub Actions enforces a 5-minute minimum interval on schedule triggers.