Lucas Merencia

it's not well documented, sorry, never tested that sleep scenario. you may try use the autorecover option: https://github.com/node-cron/node-cron/blob/master/src/scheduled-task.js#L14 ```js cron.schedule('* * * * * *', ()=> { // ... },...

actually a new version was released: https://www.npmjs.com/package/node-cron I checked the code, I think the migration to v4 looks simple, since this project is using the default options on scheduling.

> However, as far as I understand, task.execute() is effectively the same as cron.schedule, so this does not solve the problem for us. No, it's not the same at all....

Hey! It seems related to the child process using regular node.js when starting a background task. I've seen that error happening when node version was lower than v23.6.0 (if I...

I don't think we should allow opting out of this warning. It was added because apps that perform blocking I/O can cause `node-cron` to miss scheduled executions. When this happens,...

Hello @andrejcremoznik, thanks for reporting and fixing that. I took a look on it and it looks good to me, however, I think there is unit tests expecting that timeout,...

Can you upgrade to the latest node-cron version?

@wenkangwow is it duplicated on 03/08 and 04/08? It looks like a extra process running. Don't know how to simulate that.

Hello @GaneshS288, thanks for sharing this and about the analysis on cpu usage. This happens when using exactly the code you shared or it's just an example? When isolating into...

Thanks for the detailed updates. This is a strange issue, especially with the behavior changing when the internet is connected. Could it be something in the environment affecting how the...