Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Error: Something went wrong. cron reached maximum iterations. #469

Closed
MilyaushaShigapova opened this issue Feb 20, 2020 · 5 comments
Closed

Error: Something went wrong. cron reached maximum iterations. #469

MilyaushaShigapova opened this issue Feb 20, 2020 · 5 comments

Comments

@MilyaushaShigapova
Copy link

MilyaushaShigapova commented Feb 20, 2020 •
edited
Loading

what is the problem what happened?

/home/app/node_modules/cron/lib/cron.js:235

				throw new Error(


				^

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

at CronTime._getNextDateFrom (/home/app/node_modules/cron/lib/cron.js:235:12)


at CronTime.sendAt (/home/app/node_modules/cron/lib/cron.js:156:17)


at CronTime.getTimeout (/home/app/node_modules/cron/lib/cron.js:175:29)


at CronJob.start (/home/app/node_modules/cron/lib/cron.js:613:31)


at Timeout.callbackWrapper [as _onTimeout] (/home/app/node_modules/cron/lib/cron.js:665:29)


at listOnTimeout (timers.js:324:15)


at processTimers (timers.js:268:5)
@MilyaushaShigapova 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
@ncb000gt
Copy link
Member

Can you share some code to help debug?

@mryellow
Copy link

#408

@ncb000gt ncb000gt mentioned this issue Feb 25, 2020
Closed
@mikelam14
Copy link

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
@ncb000gt
GH-467 GH-478 GH-469 GH-470 GH-497 GH-498 - Allow soft warning when a…
982063f 
… hard error isn't required.

Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
@ncb000gt ncb000gt mentioned this issue May 27, 2020
Closed
@ncb000gt
Copy link
Member

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
GH-467 GH-478 GH-469 GH-470 GH-497 GH-498 - Allow soft warning when a…
7a6f93b 
… hard error isn't required.

Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
ncb000gt added a commit that referenced this issue May 28, 2020
@ncb000gt
GH-467 GH-478 GH-469 GH-470 GH-497 GH-498 - Allow soft warning when a…
b79391b 
… hard error isn't required.

Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
ncb000gt added a commit that referenced this issue Jun 2, 2020
@ncb000gt
GH-467 GH-478 GH-469 GH-470 GH-497 GH-498 - Allow soft warning when a…
e928c8c 
… hard error isn't required.

Signed-off-by: Nick Campbell <nicholas.j.campbell@gmail.com>
@intcreator
Copy link
Collaborator

closing in favor of #467

@intcreator intcreator closed this as not planned Won't fix, can't repro, duplicate, stale Feb 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@ncb000gt @mryellow @mikelam14 @intcreator @MilyaushaShigapova