-
-
Notifications
You must be signed in to change notification settings - Fork 200
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
Batch callbacks not run when job fails, then succeeds #1239
Comments
Thanks for opening this issue! I just poked at it and I think there's a bug with how a job is treated if it errors, but then later succeeds. I will dig into this more. |
oh, let me ask: Is your |
yes, and the callback works in the case where there are no errors on the original job, updating the original job |
Are you seeing this in production, or just in test with :inline execution? (I ask because the issue I discovered is specifically with :inline) |
Good question. I'm running locally in development mode. It's running under the puma web process, but I'm not sure if that means it is :inline or not. |
I just tried changing :execution_mode to :external, and still seeing the same result. |
Just wanted to briefly follow up: I think I've found the problem: When #928 was introduced, I think I overlooked how that would interact with this line:
I think the simple fix is to add |
The fix is released in https://github.com/bensheldon/good_job/releases/tag/v3.24.0 Thank you so much for reporting this! |
Wow, thanks for fixing this so quickly! |
Given the following code, the success callback is never invoked. Is that expected?
The text was updated successfully, but these errors were encountered: