Add docs for subscription retry mechanism

Signed-off-by: Albert Callarisa <albert@diagrid.io>
This commit is contained in:
Albert Callarisa 2025-08-27 09:21:59 +02:00
parent 766d8da01c
commit 093553995e
No known key found for this signature in database
GPG Key ID: 450F38BCAA761685
1 changed files with 6 additions and 0 deletions

View File

@ -120,6 +120,12 @@ Even if the message fails to deliver, or your application crashes, Dapr attempts
All Dapr pub/sub components support the at-least-once guarantee.
### Subscription startup reliability
Dapr automatically retries failed subscription startups to improve reliability during deployment scenarios. This ensures your pub/sub applications remain resilient even when facing temporary connectivity or permission issues.
When Dapr encounters errors starting subscriptions, it will show an error message in the logs and continue to try to start the subscription.
### Consumer groups and competing consumers pattern
Dapr handles the burden of dealing with consumer groups and the competing consumers pattern. In the competing consumers pattern, multiple application instances using a single consumer group compete for the message. Dapr enforces the competing consumer pattern when replicas use the same `app-id` without explicit consumer group overrides.