From f86a070731e615454507b91e99aaff4cbb2327b1 Mon Sep 17 00:00:00 2001 From: Mark Fussell Date: Mon, 1 Sep 2025 10:37:00 -0700 Subject: [PATCH] Update daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-architecture.md Signed-off-by: Mark Fussell --- .../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 5dfbfd421..214ec6d26 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 @@ -245,7 +245,7 @@ See the [Reminder usage and execution guarantees section]({{% ref "workflow-arch By default, when a client schedules a workflow, the workflow engine waits for the workflow to be fully started before returning a response to the client. Waiting for the workflow to start before returning can decrease the scheduling throughput of workflows. -When scheduling a workflow with a start time, the workflow engine will not wait for the workflow to start before returning a response to the client. +When scheduling a workflow with a start time, the workflow engine does not wait for the workflow to start before returning a response to the client. To increase scheduling throughput, consider adding a start time of "now" when scheduling a workflow. An example of scheduling a workflow with a start time of "now" in the Go SDK is shown below: