Error: Something went wrong. cron reached maximum iterations
See original GitHub issueTime 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:
- Created 4 years ago
- Reactions:8
- Comments:23 (3 by maintainers)
Top 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 >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I realized the error would show whenever my CPU utilization is too high (>9x%). That might cause some delay of code and affect something.
yes, it reappeared, though solved in
1.7
one year agocron@1.8.2