👀 Views: 187 💬 Answers: 1 📅 Created: 2025-07-23

azure-service-bus csharp message-queue C#

I'm working on a personal project and I've been banging my head against this for hours... I'm working with an scenario where messages sent to my Azure Service Bus queue are not being processed as expected after hitting the maximum delivery count. I configured the queue with a max delivery count of 5, but instead of being moved to the DeadLetter queue, the messages seem to disappear without any behavior message. Here is how I set up my Service Bus queue in C# using the Azure.Messaging.ServiceBus library: ```csharp var connectionString = "<Your_Service_Bus_Connection_String>"; var client = new ServiceBusClient(connectionString); var sender = client.CreateSender("<Your_Queue_Name>"); var message = new ServiceBusMessage("Hello, World!"); await sender.SendMessageAsync(message); ``` In my message processing function, I'm throwing an exception to simulate a processing failure: ```csharp public async Task ProcessMessageAsync(ServiceBusReceivedMessage message, CancellationToken token) { throw new Exception("Simulated failure"); } ``` I have configured the message handler like this: ```csharp var processor = client.CreateProcessor("<Your_Queue_Name>", new ServiceBusProcessorOptions() { MaxConcurrentCalls = 1, AutoCompleteMessages = false, }); processor.ProcessMessageAsync += ProcessMessageAsync; processor.ProcessErrorAsync += ErrorHandler; await processor.StartProcessingAsync(); ``` Despite the exceptions being thrown, the messages are not being routed to the DeadLetter queue, and I need to find anything in the logs indicating what might be happening. I've checked the Azure portal and confirmed that the queue settings are correct. Could this be a result of incorrect configuration or a missing step in message processing? Any insights would be greatly appreciated! This is part of a larger CLI tool I'm building. What am I doing wrong?