-
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. #469
Comments
MilyaushaShigapova
changed the title
error: Time Zone: "" - Cron String: 0 * * * * * - UTC offset: +00:00 - current Date: Wed Feb 19 2020 14:07:09 GMT+0000
Error: Something went wrong. cron reached maximum iterations.
Feb 20, 2020
Can you share some code to help debug? |
I realized the error would show whenever my CPU utilization is too high (>9x%). That might cause some delay of code and affect something. |
ncb000gt
added a commit
that referenced
this issue
May 27, 2020
I pushed up a PR with some changes to allow a "soft warning". Can you please test and report back? |
ncb000gt
added a commit
that referenced
this issue
May 28, 2020
ncb000gt
added a commit
that referenced
this issue
May 28, 2020
ncb000gt
added a commit
that referenced
this issue
Jun 2, 2020
closing in favor of #467 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
what is the problem what happened?
/home/app/node_modules/cron/lib/cron.js:235
Error: Something went wrong. cron reached maximum iterations.
Time Zone: "" - Cron String: 0 * * * * * - UTC offset: +00:00 - current Date: Wed Feb 19 2020 14:07:09 GMT+0000
The text was updated successfully, but these errors were encountered: