-
Notifications
You must be signed in to change notification settings - Fork 22
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
Steps for debugging #38
Comments
So what happened was the scheduler task failed because of bad config but it was never scheduled again until I scheduled it manually in rails console. How can we prevent this from happening? |
It should not be possible for the job to ever "go away". Were any other operations being performed - could it have been cleared down if some other jobs were being deleted for some reason? |
I've opened a PR change that will allow spec time configuration checks. Can you see if this will help with the issue you were seeing? #40 |
Version 3.2.2 released that covers invalid config checking. |
I am using this in production. After few days it has stopped scheduling new jobs.
Any steps on debugging it?
The text was updated successfully, but these errors were encountered: