-
Notifications
You must be signed in to change notification settings - Fork 189
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
best way to re-activate a job #356
Comments
Just successfully did a .update(error_count: 0, expired_at: nil) |
That update looks good to me. You're right that we should document it. Feel free to PR the docs ;)
I don't have experience with using it in Rails, but I believe you'd need to
Yeah, that's what |
What is the best procedure to re-activate a job that errored due to a system fault that has now been fixed? QueJob does a great job of retrying with backoff and eventually giving up (is that true?).
reset the error_count to 0?
nil out the expired_at date?
Oh, and should I be able to access Que::ActiveRecord::Model in Rails console? I can access Que::ActiveRecord but no Que::ActiveRecord::Model (i've added my own Rails model record to be able access it for now)
I think this would be useful practical help to anyone running live, and should go in the documentation
The text was updated successfully, but these errors were encountered: