/ cron expressions / every-minute
// cron expression reference

Cron Expression Every Minute* * * * *

* * * * *

Plain English: Every minute of every hour, every day — 1,440 times per day.

Try it in the Builder →
// how it works

How * * * * * Works

* * * * * is the most granular schedule standard Unix cron supports. Every field is a wildcard, meaning "match all values." This fires once per minute, 60 times per hour, 1,440 times per day.

Use with care — every-minute jobs can accumulate if a previous run overlaps with the next trigger. For sub-minute scheduling, use systemd timers, BullMQ, Celery, or Sidekiq instead.

Field Breakdown

FieldValueMeaning
Minute*Every minute (0–59)
Hour*Every hour
Day of month*Every day
Month*Every month
Weekday*Every day of week
// next scheduled runs (UTC)

Next 10 Run Times

Approximate run times starting from the current date. Open in the builder to see exact run times in your timezone.

00:00 00:01 00:02 00:03 00:04 00:05 00:06 00:07 00:08 00:09
// copy-paste ready examples

Platform Examples

Linux / Unix crontab
* * * * * /path/to/script.sh
GitHub Actions
# Note: GitHub Actions has a minimum interval of 5 minutes
on:
  schedule:
    - cron: '*/5 * * * *'  # use */5 instead
AWS EventBridge
cron(* * * * ? *)
Kubernetes CronJob
spec:
  schedule: "* * * * *"
node-cron (Node.js)
cron.schedule('* * * * *', () => { ... });
APScheduler (Python)
scheduler.add_job(fn, 'cron')  # defaults to every minute
// related expressions

Related Cron Expressions

Every 5 Minutes
*/5 * * * *
Every 15 Minutes
*/15 * * * *
Every 30 Minutes
*/30 * * * *
Every Hour
0 * * * *
// frequently asked questions

FAQ

Can cron run more frequently than every minute?
No — standard Unix cron only supports per-minute granularity. For sub-minute tasks use systemd timers (OnCalendar=*:*:0/30 for every 30 seconds), or a purpose-built job queue like BullMQ, Celery, or Sidekiq.
Is * * * * * the same as @minutely?
Most cron implementations do not support @minutely. Use * * * * * explicitly.
Will * * * * * cause issues if my job takes longer than a minute?
Yes — if the previous run has not finished before the next trigger fires, you may get overlapping jobs. Use file locking (flock) or check for a running process to prevent overlap.

Build or explain any cron expression

Use the free visual builder — paste an expression for a plain-English explanation, or click your way to a schedule. See the next 10 run times. No login.

Open CronBuilder →