We have an Azure Service Bus queue where a small number of messages land in the dead-letter queue after repeated processing failures. Some are caused by temporary downstream issues, while others look like genuinely bad payloads.
How do you handle dead-letter message replay without accidentally processing a message twice or sending a poison message straight back into the same cycle? I’m interested in how people separate safe retries from messages that need investigation first.
Can you answer this question?
Write Answer0 Answers