Hey @Ashok . Thanks for the question. We’ve been asked before for a “NACK” capability, to be able to send a message back to the queue. I’m gathering requirements around this feature request: what exactly would you want as expected behaviour? Since you have an exclusive queue, this receiver/consumer is the only one active, so it would simply receive the message again in callback right away. Is it that you don’t want your consumer to have any state, therefore you don’t want it to “hold on” to the message to retry again? Any guidance on your requirements would be useful. Thanks!