for a client using Wolverine, it's actually been harmful to use RetryWithCooldown() when the outstanding message runs later than expected and runs into concurrency issues with another messages. Having an error handler that pauses, then requeues in conjunction with serializing the messages could help here.
for a client using Wolverine, it's actually been harmful to use RetryWithCooldown() when the outstanding message runs later than expected and runs into concurrency issues with another messages. Having an error handler that pauses, then requeues in conjunction with serializing the messages could help here.