question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error: Something went wrong. cron reached maximum iterations

See original GitHub issue

Time Zone: "" - Cron String: 0 0,30 * * * * - UTC offset: +00:00 - current Date: Mon Mar 16 2020 16:31:21 GMT+0000

cron@1.8.2 @types/cron@1.7.2

stacktrace:

at CronTime._getNextDateFrom (/usr/src/app/node_modules/cron/lib/cron.js:235:12)
at CronTime.sendAt (/usr/src/app/node_modules/cron/lib/cron.js:156:17)
at CronTime.getTimeout (/usr/src/app/node_modules/cron/lib/cron.js:175:29)
at CronJob.start (/usr/src/app/node_modules/cron/lib/cron.js:613:31)
at Timeout.callbackWrapper [as _onTimeout] (/usr/src/app/node_modules/cron/lib/cron.js:665:29)
at listOnTimeout (internal/timers.js:549:17)
at processTimers (internal/timers.js:492:7)

index.ts:

import cron from "cron";

...

cron.job("0 0,30 * * * *", () => task(arg), undefined, true);

Issue Analytics

  • State:open
  • Created 4 years ago
  • Reactions:8
  • Comments:23 (3 by maintainers)

github_iconTop GitHub Comments

5reactions
mikelam14commented, Mar 30, 2020

I realized the error would show whenever my CPU utilization is too high (>9x%). That might cause some delay of code and affect something.

4reactions
ghostcommented, Mar 28, 2020

yes, it reappeared, though solved in 1.7 one year ago

cron@1.8.2

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: 39 0,15,30,45 * * * * - UTC offset: +00:00 - current Date: Sat Mar 28 2020 13:30:45 GMT+0000     

at CronTime._getNextDateFrom (/app/node_modules/cron/lib/cron.js:235:12)     
at CronTime.sendAt (/app/node_modules/cron/lib/cron.js:156:17)     
at CronTime.getTimeout (/app/node_modules/cron/lib/cron.js:175:29)     at CronJob.start (/app/node_modules/cron/lib/cron.js:613:31)     
at Timeout.callbackWrapper [as _onTimeout] (/app/node_modules/cron/lib/cron.js:665:29)     
at listOnTimeout (internal/timers.js:531:17)     
at processTimers (internal/timers.js:475:7)
Read more comments on GitHub >

github_iconTop Results From Across the Web

Something went wrong. cron reached maximum iterations #408
I realized the error would show whenever my CPU utilization is too high (>9x%). That might cause some delay of code and affect...
Read more >
Something went wrong. cron reached maximum iterations.
Error : Something went wrong. cron reached maximum iterations. Please open an issue (https://github.com/kelektiv/node-cron/issues/new) and ...
Read more >
Solved Cloudron 5.3.3 crashed for me, unclear why.
... Error: Something went wrong. cron reached maximum iterations. Please open an issue (https://github.com/kelektiv/node-cron/issues/new) ...
Read more >
Node-cron - Red crashed, does it need a bump in package ...
Node-cron - Red crashed, does it need a bump in package.json? ... 02:55:00 - Error: Something went wrong. cron reached maximum iterations.
Read more >
RestApps not starting with error - FreePBX Phone Apps
Something went wrong. cron reached maximum iterations. This is an error from crond, so there's something going wrongly in your crontab setup.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found