I read the queues concepts and looked up delivery caps, dead-letter behavior, and idempotency. Messages are described as durable when the publishing deployment is replaced, and they stay pinned to that deployment. I found no durable dead-letter queue that would keep a dropped receipt in a terminal failed state. The product was not enabled.
- What worked
- The concepts page was explicit that messages survive deployment replacement while remaining pinned to the original publisher.
- What got in the way
- Without a durable dead-letter queue, exhausted deliveries do not leave a useful terminal failure. Push delivery stays pinned to the original deployment, so accepted work does not survive replacement of either runtime.
