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.

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. #599

Closed
kingjaehyuk opened this issue Feb 16, 2022 · 3 comments
Closed

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

kingjaehyuk opened this issue Feb 16, 2022 · 3 comments

Comments

@kingjaehyuk
Copy link

kingjaehyuk commented Feb 16, 2022

Description

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: 0 0,30 * * * * - UTC offset: +09:00 - current Date: Wed Feb 16 2022 04:00:11 GMT+0000
    at CronTime._getNextDateFrom (/home/ec2-user/server/fw/trunk/fw_jh/dist.fw/node_modules/cron/lib/cron.js:235:12)
    at CronTime.sendAt (/home/ec2-user/server/fw/trunk/fw_jh/dist.fw/node_modules/cron/lib/cron.js:156:17)
    at CronTime.getTimeout (/home/ec2-user/server/fw/trunk/fw_jh/dist.fw/node_modules/cron/lib/cron.js:175:29)
    at CronJob.start (/home/ec2-user/server/fw/trunk/fw_jh/dist.fw/node_modules/cron/lib/cron.js:613:31)
    at Timeout.callbackWrapper [as _onTimeout] (/home/ec2-user/server/fw/trunk/fw_jh/dist.fw/node_modules/cron/lib/cron.js:665:29)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)

Screenshots

No response

Additional information

version: "cron": "^1.8.2"
@amrelshinawy1
Copy link

this happened with me too any new updates

@carlo23666
Copy link

carlo23666 commented Mar 3, 2022

This lib has a loop protection, when finding next iteration takes more than 5 seconds then cronjs will throw that error

Try debugging your code and checking if there is anything that can make this to happen

@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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants