Closed jdalrymple closed 4 years ago
Thanks for the heads up, will look at this ASAP unless @shadowgate15 gets to it before myself.
Please upgrade to v3.1.0 as these issues are fixed. I have also published an npm deprecation notice for older versions.
If you don't want the job to start immediately, either set timeout: false
as a global or job-specific option.
Regardless of the interval, the task is run on start. I dont think i missed an option to skip running on start.