From 90af1972f72428e2481f3494329c20224b490c5e Mon Sep 17 00:00:00 2001 From: Hannah Hunter <94493363+hhunter-ms@users.noreply.github.com> Date: Fri, 9 Feb 2024 11:10:15 -0500 Subject: [PATCH] Update daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-architecture.md Co-authored-by: Chris Gillum Signed-off-by: Hannah Hunter <94493363+hhunter-ms@users.noreply.github.com> --- .../building-blocks/workflow/workflow-architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-architecture.md b/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-architecture.md index 8d9494cd3..dffea560d 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-architecture.md +++ b/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-architecture.md @@ -145,7 +145,7 @@ Different state store implementations may implicitly put restrictions on the typ Similarly, if a state store imposes restrictions on the size of a batch transaction, that may limit the number of parallel actions that can be scheduled by a workflow. -Workflow state can be purged from a state store, purging all its history. Purging removes all metadata related to a specific workflow instance. +Workflow state can be purged from a state store, including all its history. Each Dapr SDK exposes APIs for purging all metadata related to specific workflow instances. ## Workflow scalability