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

Something went wrong. cron reached maximum iterations #497

Closed
amit221 opened this issue May 14, 2020 · 3 comments
Closed

Something went wrong. cron reached maximum iterations #497

amit221 opened this issue May 14, 2020 · 3 comments

Comments

@amit221
Copy link

amit221 commented May 14, 2020

Time Zone: "" - Cron String: 1 0,10,20,30,40,50 * * * * - UTC offset: +00:00 - current Date: Thu May 14 2020 05:00:20 GMT+0000

@validkeys
Copy link

I actually just received this issue as well:

Time Zone: "" - Cron String: 0 * * * * * - UTC offset: -04:00 - current Date: Thu May 14 2020 13:33:06 GMT+0000

ncb000gt added a commit that referenced this issue May 27, 2020
… hard error isn't required.

Signed-off-by: Nick Campbell <[email protected]>
@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
… hard error isn't required.

Signed-off-by: Nick Campbell <[email protected]>
ncb000gt added a commit that referenced this issue May 28, 2020
… hard error isn't required.

Signed-off-by: Nick Campbell <[email protected]>
ncb000gt added a commit that referenced this issue Jun 2, 2020
… hard error isn't required.

Signed-off-by: Nick Campbell <[email protected]>
@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