cron

node-cron

Cron is a tool that allows you to execute something on a schedule. This is typically done using the cron syntax. We allow you to:

• execute a function whenever your scheduled job triggers
• execute a job external to the javascript process (like a system command) using child_process
• use a Date or Luxon DateTime object instead of cron syntax as the trigger for your callback
• use an additional slot for seconds (leaving it off will default to 0 and match the Unix behavior)

Installation

npm install cron

Migrating from v2 to v3

In version 3 of this library, we migrated to TypeScript, aligned our cron patterns format with the UNIX standard, and released some other breaking changes. See below for the changes you need to make when upgrading:

Migrating from v2 to v3

Month & day-of-week indexing changes

Month indexing went from 0-11 to 1-12. So you need to increment all numeric months by 1.

For day-of-week indexing, we only added support for 7 as Sunday, so you don't need to change anything!

CronJob changes

• constructor no longer accepts an object as its first and only params. Use CronJob.from(argsObject) instead.
• callbacks are now called in the order they were registered.

Removed methods

• removed job() method in favor of new CronJob(...args) / CronJob.from(argsObject)

• removed time() method in favor of new CronTime()

Usage (basic cron usage)

import { CronJob } from 'cron';
const job = new CronJob(
	'* * * * * *',
	function () {
		console.log('You will see this message every second');
	},
	null,
	true,
	'America/Los_Angeles'
);
// job.start() - See note below when to use this

Note - In the example above, the 4th parameter of CronJob() automatically starts the job on initialization. If this parameter is falsy or not provided, the job needs to be explicitly started using job.start().

There are more examples available in this repository at: /examples

Available Cron patterns

Asterisks e.g. *
Ranges e.g. 1-3,5
Steps e.g. */2

Read up on cron patterns here. Note the examples in the link have five fields, and 1 minute as the finest granularity, but this library has six fields, with 1 second as the finest granularity.

There are tools that help when constructing your cronjobs. You might find something like https://crontab.guru/ or https://cronjob.xyz/ helpful. But, note that these don't necessarily accept the exact same syntax as this library, for instance, it doesn't accept the seconds field, so keep that in mind.

Cron Ranges

This library follows the UNIX Cron format, with an added field at the beginning for second granularity.

field          allowed values
-----          --------------
second         0-59
minute         0-59
hour           0-23
day of month   1-31
month          1-12 (or names, see below)
day of week    0-7 (0 or 7 is Sunday, or use names)

Names can also be used for the 'month' and 'day of week' fields. Use the first three letters of the particular day or month (case does not matter). Ranges and lists of names are allowed.
Examples: "mon,wed,fri", "jan-mar".

Gotchas

• Millisecond level granularity in JS Date or Luxon DateTime objects: Because computers take time to do things, there may be some delay in execution. This should be on the order of milliseconds. This module doesn't allow MS level granularity for the regular cron syntax, but does allow you to specify a real date of execution in either a javascript Date object or a Luxon DateTime object. When this happens you may find that you aren't able to execute a job that should run in the future like with new Date().setMilliseconds(new Date().getMilliseconds() + 1). This is due to those cycles of execution above. This wont be the same for everyone because of compute speed. When we tried it locally we saw that somewhere around the 4-5 ms mark was where we got consistent ticks using real dates, but anything less than that would result in an exception. This could be really confusing. We could restrict the granularity for all dates to seconds, but felt that it wasn't a huge problem so long as you were made aware. If this becomes more of an issue, We can revisit it.
• Arrow Functions for onTick: Arrow functions get their this context from their parent scope. Thus, if you use them, you will not get the this context of the cronjob. You can read a little more in issue GH-47

API

Parameter Based

• sendAt - tells you when a CronTime will be run.
• timeout - tells you when the next timeout is.
• CronJob
  • constructor(cronTime, onTick, onComplete, start, timeZone, context, runOnInit, utcOffset, unrefTimeout)
    • cronTime - [REQUIRED] - The time to fire off your job. This can be in the form of cron syntax or a JS Date object.
    • onTick - [REQUIRED] - The function to fire at the specified time. If an onComplete callback was provided, onTick will receive it as an argument. onTick may call onComplete when it has finished its work.
    • onComplete - [OPTIONAL] - A function that will fire when the job is stopped with job.stop(), and may also be called by onTick at the end of each run.
    • start - [OPTIONAL] - Specifies whether to start the job just before exiting the constructor. By default this is set to false. If left at default you will need to call job.start() in order to start the job (assuming job is the variable you set the cronjob to). This does not immediately fire your onTick function, it just gives you more control over the behavior of your jobs.
    • timeZone - [OPTIONAL] - Specify the time zone for the execution. This will modify the actual time relative to your time zone. If the time zone is invalid, an error is thrown. By default (if this is omitted) the local time zone will be used. You can check the various time zones format accepted in the Luxon documentation. Note: This parameter supports minutes offsets, e.g. UTC+5:30. Note: Cannot be used together with utcOffset.
    • context - [OPTIONAL] - The context within which to execute the onTick method. This defaults to the cronjob itself allowing you to call this.stop(). However, if you change this you'll have access to the functions and values within your context object.
    • runOnInit - [OPTIONAL] - This will immediately fire your onTick function as soon as the requisite initialization has happened. This option is set to false by default for backwards compatibility.
    • utcOffset - [OPTIONAL] - This allows you to specify the offset of your time zone rather than using the timeZone param. This should be an integer representing the number of minutes offset (like 120 for +2 hours or -90 for -1.5 hours). Note: Cannot be used together with timeZone.
    • unrefTimeout - [OPTIONAL] - If you have code that keeps the event loop running and want to stop the node process when that finishes regardless of the state of your cronjob, you can do so making use of this parameter. This is off by default and cron will run as if it needs to control the event loop. For more information take a look at timers#timers_timeout_unref from the NodeJS docs.
  • from (static) - Create a new CronJob object providing arguments as an object. See argument names and descriptions above.
  • start - Runs your job.
  • stop - Stops your job.
  • setTime - Stops and changes the time for the CronJob. Param must be a CronTime.
  • lastDate - Tells you the last execution date.
  • nextDate - Provides the next date that will trigger an onTick.
  • nextDates - Provides an array of the next set of dates that will trigger an onTick.
  • fireOnTick - Allows you to override the onTick calling behavior. This matters so only do this if you have a really good reason to do so.
  • addCallback - Allows you to add onTick callbacks. Callbacks are run in the order they are registered.
• CronTime
  • constructor(time, zone, utcOffset)
    • time - [REQUIRED] - The time to fire off your job. This can be in the form of cron syntax or a JS Date object.
    • zone - [OPTIONAL] - Same as timeZone from CronJob parameters.
    • utcOffset - [OPTIONAL] - Same as utcOffset from CronJob parameters.

Community

Join the Discord server! Here you can discuss issues and get help in a more casual forum than GitHub.

Contributing

This project is looking for help! If you're interested in helping with the project, please take a look at our contributing documentation.

Submitting Bugs/Issues

Please have a look at our contributing documentation, it contains all the information you need to know before submitting an issue.

Acknowledgements

This is a community effort project. In the truest sense, this project started as an open source project from cron.js and grew into something else. Other people have contributed code, time, and oversight to the project. At this point there are too many to name here so we'll just say thanks.

Special thanks to Hiroki Horiuchi, Lundarl Gholoi and koooge for their work on the DefinitelyTyped typings before they were imported in v2.4.0.

License

MIT