Document that ordering is lost for dead-lettered messages#128317
Document that ordering is lost for dead-lettered messages#128317lailabougria wants to merge 1 commit intoMicrosoftDocs:mainfrom
Conversation
Added section on MaxDeliveryCount to explain message handling and dead-lettering in sessions.
|
@lailabougria : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit d382b8c: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
There was a problem hiding this comment.
Pull request overview
Adds documentation clarifying that session message ordering is not preserved if a dead-lettered message is later resubmitted to the original entity for reprocessing.
Changes:
- Introduces a new section describing how
MaxDeliveryCountaffects session processing and dead-lettering. - Documents that resubmitting a dead-lettered message back to the queue breaks the original message ordering for the session.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
|
|
||
| ## MaxDeliveryCount | ||
|
|
||
| When failures occur, and the message is abandoned, it will be made available again on the session for consumption by a receiver until the MaxDeliveryCount is exceeded. When the MaxDeliveryCount is exceeded, the failing message is dead-lettered, and the receiver will continue receiving subsequent messages from the session. If and when the dead-lettered message is moved back to the queue for reprocessing, the original order in which the messages were received is lost. |
When message processing fails for a message in a session, the message is moved to the dead-letter queue once the MaxDeliveryCount is exceeded. At this point, a receiver can continue consuming messages from that session.
Should the user ever resend the failed message from the dead-letter queue to the original queue, the original ordering is lost.