An umber-wash payload is malformed and reappears after every visibility timeout. How should the developer detect and handle this poison message?
Select an answer to reveal the explanation.
Short Explanation
If dequeue count keeps climbing, that message is poison. Log it or move it aside — Functions even has a poison-queue convention — instead of looping forever.
Full Explanation
Queue Storage exposes a dequeue count that rises each time a message is retrieved. Applications (and Azure Functions poison-message handling) use that count to quarantine or log poison payloads. Service Bus DLQ applies to Service Bus entities, not Storage queues; Event Hubs TUs and disabling telemetry do not handle poison messages.