-
Notifications
You must be signed in to change notification settings - Fork 622
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
Comments
I actually just received this issue as well:
|
ncb000gt
added a commit
that referenced
this issue
May 27, 2020
… hard error isn't required. Signed-off-by: Nick Campbell <[email protected]>
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]>
closing in favor of #467 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: