Skip to content

feat: add retry and dead-letter queue to receive operation - #1236

Open
nashjain wants to merge 2 commits into
asyncapi:masterfrom
specmatic:master
Open

feat: add retry and dead-letter queue to receive operation#1236
nashjain wants to merge 2 commits into
asyncapi:masterfrom
specmatic:master

Conversation

@nashjain

@nashjain nashjain commented Aug 6, 2026

Copy link
Copy Markdown

Add retry and DLQ to receive operation

Related issue(s)

Closes #1234

What changed

Adds an RFC proposal for optional top-level retry and deadLetter paths 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

  • Adds retry and deadLetter as siblings of reply on the Operation Object.
  • Defines retry routing, retry strategies, and dead-letter routing.
  • Includes focused YAML examples for both recovery paths.

Validation

  • Embedded-example validation
  • Markdown lint

RFC status

This pull request is for RFC 1 proposal. The design remains open for community discussion, including naming and detailed semantics.

@nashjain nashjain added 📣 RFC document PR creates or changes document inside "rfc" folder 💡 Proposal (RFC 1) RFC Stage 1 (See CONTRIBUTING.md) and removed 📣 RFC document PR creates or changes document inside "rfc" folder labels Aug 6, 2026
@sonarqubecloud

sonarqubecloud Bot commented Aug 6, 2026

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

💡 Proposal (RFC 1) RFC Stage 1 (See CONTRIBUTING.md)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Feature Request: model retry policies and dead-letter routing on operations

1 participant