Error: Something went wrong. cron reached maximum iterations.

[shivam-postman]

We got the following error message:
Error: Something went wrong. cron reached maximum iterations.

Along with it, there was this string:
Time Zone: "" - Cron String: 0,15,30,45 * * * * * - UTC offset: +00:00 - current Date: Wed Feb 12 2020 04:07:14 GMT+0000

It'd be great if you guys can let me know some whereabouts of it; would be helpful in finding the side effects of the said error. Thanks.

[mryellow]

#408

[pddivine]

I ran into the same issue as well:

Error: Something went wrong. cron reached maximum iterations. Please open an issue (https://github.com/kelektiv/node-cron/issues/new) and provide the following string Time Zone: "" - Cron String: 0,15,30,45 * * * * * - UTC offset: +00:00 - current Date: Mon May 04 2020 01:05:26 GMT+0000

[ncb000gt]

I pushed up a PR with some changes to allow a "soft warning". Can you please test and report back?

[kasir-barati]

@pddivine @shivam-postman Can you give me a script which reproduce/potentially reproduce the same issue?

[intcreator]

has this been an problem since the move from Moment to Luxon? if not we can close this issue

[sheerlox]

@intcreator are you referring to #499? While I definitely agree with you, at the same time the comment made by Nick about this also makes sense to me.
The only way I see (for now and with my limited knowledge of the codebase) to tackle this issue is to understand the conditions under which an infinite loop would exist and write safeguards specific to that. What do you think?

[intcreator]

yeah that's the issue I was referring to.

maybe instead of crashing we can restart the cron job with a warning? that way the infinite loop is prevented but the cron job can still be running afterward

[cexedev]

Has anyone found the fix yet,
let resetNotificationFlagIfFailed = new CronJob(*/20 * * * * *, async function () { ... MY CODE HERE }, null, true, "Australia/Brisbane" );

This is how I've running a cronjob and this is the error i am getting
Error: Something went wrong. It took over five seconds to find the next execution time for the cron job. Please refer to the canonical issue (https://github.com/kelektiv/node-cron/issues/467) and provide the following string if you would like to help debug: Time Zone: "" - Cron String: 0,15,30,45 * * * * * - UTC offset: 600

[mryellow]

This package works in the cases where node-cron does not.

https://github.com/harrisiirak/cron-parser

I'd suggest moving to it entirely or replacing _getNextDateFrom with this library.

[jakguru]

Got this error: Error: Something went wrong. It took over five seconds to find the next execution time for the cron job.
Here's the string that it asked for:

Time Zone: "" - Cron String: 0 * * * * * - UTC offset: 0 - current Date: 2023-07-13T22:18:41.049+00:00
Node.js v18.16.1

[ncb000gt]

🎉 This issue has been resolved in version 2.4.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[sheerlox]

Hey there! As stated above, we released a fix for this issue in v2.4.1 🎉

We expect this change to fix the majority of cases you encountered, which we believe were mostly related to low resources environments.

Please update to that version, and open a new issue if you encounter a similar issue again (if no one opened one already).

[ncb000gt]

🎉 This issue has been resolved in version 3.0.0-beta.2 🎉

The release is available on:

• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[olegktrnd]

I'm still encountering this issue. Here's what the full error looks like:

Error: Something went wrong. It took over five seconds to find the next execution time for the cron job.
                            Please refer to the canonical issue (https://github.com/kelektiv/node-cron/issues/467) and provide the following string if you would like to help debug:
                            Time Zone: "" - Cron String: 0,10,20,30,40,50 * * * * * - UTC offset: 0
                            - current Date: 2024-04-30T00:25:28.650+00:00
   at CT._getNextDateFrom (/opt/app/node_modules/cron/lib/time.js:272:12)
   at CT.sendAt (/opt/app/node_modules/cron/lib/time.js:185:17)
   at CT.getTimeout (/opt/app/node_modules/cron/lib/time.js:202:29)
   at CJ.start (/opt/app/node_modules/cron/lib/job.js:119:31)
   at Timeout.callbackWrapper [as _onTimeout] (/opt/app/node_modules/cron/lib/job.js:172:11)
   at listOnTimeout (node:internal/timers:564:17)
   at processTimers (node:internal/timers:507:7)>

My node-cron version is v3.0.3.
I get this error about 2-3 times a day. Any ideas what could be causing it?

[sheerlox]

Hi, this bug was fixed (and the error message you shared was removed) in v2.4.1, so upgrading to (at least) that version will resolve your issue.

[dipakpandey7]

My node-cron version is "cron": "^2.1.0",
I get this error about 2-3 times a day. Any ideas what could be causing in and how to solve this issue

[sheerlox]

@dipakpandey7 your version is probably pinned in your package manager lock file, so the same recommendation as above apply