Execute Automation Tasks Every Minute | CronBase

cron expression Standard
$ */1 * * * *

Every single minute, endlessly throughout the day, every day of the year.

This cron expression schedules a command to execute once every single minute of every hour, day, month, and day of the week. It represents the highest default frequency available in standard cron engines, commonly utilized for real-time monitoring, rapid queue processing, health checks, and high-frequency data ingestion pipelines.

Minute
*/1
Hour
*
Day of Month
*
Month
*
Day of Week
*

Next 5 Runs

  • in 41s
  • in 1m 41s
  • in 2m 41s
  • in 3m 41s
  • in 4m 41s

* Tools

Code & Implementations

nodejs
const cron = require('node-cron');
let isRunning = false;

cron.schedule('*/1 * * * *', async () => {
    if (isRunning) {
        console.warn('Previous execution still active. Skipping run.');
        return;
    }
    isRunning = true;
    try {
        console.log('Executing high-frequency polling task...');
        await new Promise(resolve => setTimeout(resolve, 5000));
    } catch (error) {
        console.error('Task failed:', error);
    } finally {
        isRunning = false;
    }
});
Setup notes

Install node-cron via npm, run the script as a daemon using pm2 or systemd to ensure continuous execution.

Partner BetterStack

Monitor this schedule in production

Get alerted the moment this cron job fails, is late, or doesn't run. BetterStack tracks execution, duration, and output — no infrastructure required.

Platform Equivalents

AWS EventBridge

Standard cron expressions often need conversion for AWS EventBridge schedules.

EventBridge Rule
cron(*/1 * * * ? *)

Systemd Timer

OnCalendar*-*-* *:00/1:00

my-task.timer
[Unit]
Description=Timer for cron expression: */1 * * * *

[Timer]
OnCalendar=*-*-* *:00/1:00
Persistent=true

[Install]
WantedBy=timers.target

Frequently Asked Questions

What happens if a job takes longer than one minute?

In a standard setup, a new instance will start anyway, potentially leading to race conditions or server overload. It is highly recommended to use a lock mechanism like flock, Redis lock, or Kubernetes' Forbid policy to prevent overlapping.

Does standard cron support sub-minute execution?

No, standard Unix cron's minimum resolution is one minute. If you need sub-minute execution (e.g., every 30 seconds), you must use a systemd service with a timer, or run a persistent background daemon that sleeps inside a loop.

How does timezone change affect an every-minute cron job?

Timezone changes (like Daylight Saving Time shifts) do not affect the frequency of an every-minute cron job. It will continue to execute exactly once every 60 seconds regardless of the clock shifting forward or backward.

Will this high frequency cause high CPU overhead?

The cron daemon itself consumes negligible CPU to trigger the task. However, the script or application being executed can cause high system load if it initializes heavy frameworks, database connections, or VM runtimes every single minute.

How do I monitor if my minute-by-minute cron job fails?

Since it runs frequently, traditional log checking is tedious. Implement a dead-man's snitch (e.g., Healthchecks.io) that expects a ping every minute, or route stderr to an enterprise alerting tool like Sentry or PagerDuty.

* Explore

Related expressions you might need

Was this helpful?

Last verified: