feat: add retry and dead-letter queue to receive operation - #1236
Open
nashjain wants to merge 2 commits into
Open
feat: add retry and dead-letter queue to receive operation#1236nashjain wants to merge 2 commits into
nashjain wants to merge 2 commits into
Conversation
nashjain
requested review from
GreenRover,
asyncapi-bot-eve,
char0n,
dalelane and
derberg
as code owners
August 6, 2026 10:15
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Add retry and DLQ to receive operation
Related issue(s)
Closes #1234
What changed
Adds an RFC proposal for optional top-level
retryanddeadLetterpaths on receive operations.Why
AsyncAPI currently cannot describe the observable recovery path for failed message processing. This proposal makes retry policy and dead-letter routing explicit while keeping broker-specific behavior in protocol bindings.
Implementation
retryanddeadLetteras siblings ofreplyon the Operation Object.Validation
RFC status
This pull request is for RFC 1 proposal. The design remains open for community discussion, including naming and detailed semantics.