-
Notifications
You must be signed in to change notification settings - Fork 622
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Something went wrong. cron reached maximum iterations. #467
Comments
I ran into the same issue as well:
|
… hard error isn't required. Signed-off-by: Nick Campbell <[email protected]>
I pushed up a PR with some changes to allow a "soft warning". Can you please test and report back? |
… hard error isn't required. Signed-off-by: Nick Campbell <[email protected]>
… hard error isn't required. Signed-off-by: Nick Campbell <[email protected]>
… hard error isn't required. Signed-off-by: Nick Campbell <[email protected]>
@pddivine @shivam-postman Can you give me a script which reproduce/potentially reproduce the same issue? |
has this been an problem since the move from Moment to Luxon? if not we can close this issue |
@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. |
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 |
Changelog: Try to catch errors from cron library related to kelektiv/node-cron#467
Has anyone found the fix yet, This is how I've running a cronjob and this is the error i am getting |
This package works in the cases where https://github.com/harrisiirak/cron-parser I'd suggest moving to it entirely or replacing |
Got this error: Time Zone: "" - Cron String: 0 * * * * * - UTC offset: 0 - current Date: 2023-07-13T22:18:41.049+00:00 |
🎉 This issue has been resolved in version 2.4.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Hey there! As stated above, we released a fix for this issue in 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). |
🎉 This issue has been resolved in version 3.0.0-beta.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Changelog: FIX: Update crom to 2.4.1 hopefully fixing kelektiv/node-cron#467
* update cron dependency relating to issue kelektiv/node-cron#467
I'm still encountering this issue. Here's what the full error looks like:
My node-cron version is v3.0.3. |
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 your version is probably pinned in your package manager lock file, so the same recommendation as above apply |
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.
The text was updated successfully, but these errors were encountered: