You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed in #425 it is sometimes useful to do some special handling using the on_failure callback after the last retry. However, at the moment, the on_failure callback does not have any way to dynamically determine if the current retry is the last.
In other words, I think it could be useful to either pass the max_retries information in the message options or add another callback on_last_failure.
Unless I'm missing something, I think the first option should be fairly straightforward to implement by adding a before_enqueue method to the Retries middleware
As discussed in #425 it is sometimes useful to do some special handling using the
on_failure
callback after the last retry. However, at the moment, theon_failure
callback does not have any way to dynamically determine if the current retry is the last.In other words, I think it could be useful to either pass the
max_retries
information in the message options or add another callbackon_last_failure
.Unless I'm missing something, I think the first option should be fairly straightforward to implement by adding a
before_enqueue
method to theRetries
middlewareIf you think this could be a useful feature and that the proposed solution makes sense, I'd be happy to open a PR with the change.
As a workaround I'm currently retrieving the actor in the
on_failure
handlerThe text was updated successfully, but these errors were encountered: