Is it possible to have different retry policy for different message types?

I’m trying to emulate request-response pattern with NSB and want to completely remove any retry for the request side commands. And use default policy for the rest of commands and events. Is It possible?

Hi @alewmt

You can inject a custom recoverability policy and use the incoming error context to retrieve the message type header. Finally based on the message type header you can decide how and if the message should be retried.