-
Notifications
You must be signed in to change notification settings - Fork 24
Description
Hit the 403 wall and couldn't branch then push example code of being able to schedule with an IRetryStep wrapping the DefaultRetryStep. So look a this Gist (https://gist.github.com/MatthewDavidCampbell/93429afa631545981257eac987bfc6da).
We had situations in our distributed solution against the Azure Service Bus where first level exceptions got received again too fast. The distributed applications hadn't settled yet and usually needed just a couple seconds to stabile when a retry would work. So we (right or wrong) introduced a scheduled retry that added a delay. That worked for us. It is hard linked to the DefaultRetryStep logic (specifically error tracking + how Failed Fast and second level retries are handled) which is why we engulfed it. Also there was a loophole in the Azure Service Bus ITransport implementation where the primary NACK delegate could be short-circuited.
If anybody else thinks this might be useful then let me know how to push or do a PR. Thanks in advance.