From 0759b92798e3d3c4abf0fc861cc94ed57b3b46aa Mon Sep 17 00:00:00 2001 From: yaron2 Date: Mon, 25 Sep 2023 22:19:56 -0700 Subject: [PATCH] add outboxDiscardWhenMissingState clarification Signed-off-by: yaron2 --- .../building-blocks/state-management/howto-outbox.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/daprdocs/content/en/developing-applications/building-blocks/state-management/howto-outbox.md b/daprdocs/content/en/developing-applications/building-blocks/state-management/howto-outbox.md index 10fb9a58b48..313c4e41766 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/state-management/howto-outbox.md +++ b/daprdocs/content/en/developing-applications/building-blocks/state-management/howto-outbox.md @@ -51,8 +51,8 @@ spec: | --------------------|-------------|---------------|------------------------------------------------------- | | outboxPublishPubsub | Yes | N/A | Sets the name of the pub/sub component to deliver the notifications when publishing state changes | outboxPublishTopic | Yes | N/A | Sets the topic to send the state changes to on the pub/sub configured with `outboxPublishPubsub`. The message body will be a state transaction item for an insert or update operation -| outboxPubsub | No | `outboxPublishPubsub` | Sets the pub/sub component to use by Dapr to coordinate the state and pub/sub transactions. If not set, the pub/sub component configured with `outboxPublishPubsub` is used. This is useful if you want to separate the pub/sub component used to send the notification state changes from the one used to coordinate the transaction. -| outboxDiscardWhenMissingState | No | `false` | By setting `outboxDiscardWhenMissingState` to `true`, Dapr will discard the transaction if it cannot find the state in the database and does not retry again. +| outboxPubsub | No | `outboxPublishPubsub` | Sets the pub/sub component to use by Dapr to coordinate the state and pub/sub transactions. If not set, the pub/sub component configured with `outboxPublishPubsub` is used. This is useful if you want to separate the pub/sub component used to send the notification state changes from the one used to coordinate the transaction +| outboxDiscardWhenMissingState | No | `false` | By setting `outboxDiscardWhenMissingState` to `true`, Dapr will discard the transaction if it cannot find the state in the database and does not retry again. This setting can be useful if the state store data has been deleted for any reason before Dapr was able to deliver the message and you would like Dapr to drop the items from the pub/sub and stop retrying to fetch the state ### Combining outbox and non-outbox messages on the same state store