BackendBench
Coffee

Home โ€บ node-cron โ€บ Every minute

node-cron cron

node-cron cron expression: every minute

To run a node-cron job every minute, use:

* * * * *

Every minute.

Your week at a glance
fewer more runs

Upcoming runs

#LocalUTCFrom now

Copy-ready code

Why use this schedule

The fastest schedule most cron systems allow. It suits near-real-time polling where waiting five minutes is too slow.

First runs, as an example

Starting from 1 January 2027, evaluated in UTC:

#Date and time (UTC)
1Fri, 01 Jan 2027, 00:00:00
2Fri, 01 Jan 2027, 00:01:00
3Fri, 01 Jan 2027, 00:02:00
4Fri, 01 Jan 2027, 00:03:00
5Fri, 01 Jan 2027, 00:04:00
6Fri, 01 Jan 2027, 00:05:00

Every minute in every dialect

SystemExpression
node-cron (this page)* * * * *
Quartz0 * * * * ?
Spring0 * * * * *
Crontab* * * * *
Kubernetes* * * * *
AWS EventBridge* * * * ? *
Jenkins* * * * *
Apache Airflow* * * * *
Azure Functions0 * * * * *
Google Cloud Scheduler* * * * *

Need to translate a different expression? Use the cron converter.

Ready-to-use node-cron config

Drop this into your project. The expression is the one above.

node-cron task
import cron from 'node-cron';

cron.schedule('* * * * *', () => {
  console.log('running a task');
}, { timezone: 'UTC' });

The node-cron fields, in order: second (0-59), minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-7, 0 and 7 = Sunday).

Things to watch out for in node-cron

The common mistake with this schedule

A job that takes longer than one minute will overlap with the next run. Guard against it with a lock, Quartz @DisallowConcurrentExecution, or concurrencyPolicy: Forbid in Kubernetes.

Frequently asked questions

How do I run a node-cron job every minute?

Use * * * * *. Every minute.

What is the every minute cron expression in other systems?

Quartz: 0 * * * * ?; Spring: 0 * * * * *; Crontab: * * * * *. The table on this page lists every dialect.

Which time zone does node-cron use for this schedule?

node-cron uses the server time zone unless you pass { timezone: "Asia/Kolkata" }. Its documentation advises timezone: "UTC" for jobs that must not skip or repeat when clocks change.

Similar node-cron schedules

More tools you might need