Skip to content
Discussion options

You must be logged in to vote

Poison message handling is something we've been wanting to implement as a built-in feature for a while. I'm not sure if that's what you're looking for, but here is an issue tracking this potential feature: #338.

However, in my application, I have been noticing from occurrences where messages with a high dequeue count in the storage.

If you're running your app in the Azure Functions hosted service and haven't done so already, I recommend taking a look at the "Diagnose and Solve Problems" blade in the Azure portal when navigating to your function app. There is a "Durable Functions" detector which can point out a few potential causes of this problem, like application restarts, internal err…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by cgillum
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants