Skip to content

docs(pubsub/rabbitmq): document graceful shutdown NACK behavior #5245

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kayvonkhosrowpour wants to merge 2 commits into
base: v1.18
Choose a base branch
from
Open

docs(pubsub/rabbitmq): document graceful shutdown NACK behavior #5245

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0bad78a
docs(pubsub/rabbitmq): document graceful shutdown NACK behavior
kkhosrowpour Jul 13, 2026
db27cd1
Merge branch 'v1.18' into fix/rabbitmq-nack-graceful-shutdown
marcduiker Jul 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions ...cs/content/en/reference/components-reference/supported-pubsub/setup-rabbitmq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -482,6 +482,16 @@ spec:
To enable [message properties](https://www.rabbitmq.com/docs/publishers#message-properties) being published in the metadata, set the `publishMessagePropertiesToMetadata` field to `"true"` in the component spec.
This will include properties such as message ID, timestamp, and headers in the metadata of the published message.

## Graceful shutdown behavior

When the Dapr runtime receives a shutdown signal, in-flight RabbitMQ messages whose handler context is cancelled (for example, because `block-shutdown-duration` has expired) are left **unacknowledged**. The component does not send a NACK in this case.

Leaving messages unacknowledged means that when the AMQP connection closes as part of shutdown, RabbitMQ automatically redelivers those messages to another available consumer. This prevents messages from being incorrectly routed to the dead-letter queue (DLQ) solely because the sidecar shut down while processing them.

{{% alert title="Note" color="primary" %}}
This behavior only applies when the message handler returns an error due to context cancellation. If the handler returns a real application error with a live context, the message is still NACKed as usual (and routed to the DLQ if `enableDeadLetter: true` and `requeueInFailure: false`).
{{% /alert %}}

## Related links

- [Basic schema for a Dapr component]({{% ref component-schema %}}) in the Related links section
Expand Down