Azure / Azure/azure-functions-dotnet-worker
DeadLetterReason and DeadLetterErrorDescription not store when using ServiceBusMessageActions.DeadLetterMessageAsync
- Dominant language
- C#
- Stars
- 466
- Forks
- 215
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 7
Description
### Description
In our Azure function app code (.net 8 isolated mode) , autocompletemessages = off and manual deadlettering is done.
I noticed that when using ServiceBusMessageActions.DeadLetterMessageAsync and providing the DeadLetterReason and DeadLetterDescription it will fail to store it intermittently.
I've included a repro solution in the attachment.
### Steps to reproduce
[DeadLetterRepro.zip](https://github.com/user-attachments/files/17661120/DeadLetterRepro.zip)
Make sure you have properly configured the connection strings in settings and program and set the queue name.
It is a repro solution with an azure function app.
It accepts requests using an http trigger and that will put messages on a queue.
A service bus trigger will react on it and then deadletter it.
After this a second trigger is retrieving the deadletter and logging it. If reason or description is empty, you'll see an error logged.
Just keep sending until it reports an error.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.