From d4d01996d5fb14ac2b40f04dfb75ab7180188de6 Mon Sep 17 00:00:00 2001 From: Bilgin Ibryam Date: Thu, 11 Sep 2025 16:45:50 +0100 Subject: [PATCH] Update daprdocs/content/en/developing-applications/building-blocks/state-management/howto-outbox.md Co-authored-by: Mark Fussell Signed-off-by: Bilgin Ibryam --- .../building-blocks/state-management/howto-outbox.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 6eec8be5a..3cd4b8264 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 @@ -41,7 +41,7 @@ This is the sequence of interactions: 3. The state and a transaction marker are written atomically in the same state store. Both the business data and the marker are committed in the same transaction, preventing partial writes. -4. Application receives a success response after the commit. +4. The application receives a success response after the transaction commits. At this point, the application can continue, knowing state is saved and the event intent is guaranteed. 5. Background subscriber reads the intent message.