From 1048cd847f4c79407be1185014bf6e979c476a9f Mon Sep 17 00:00:00 2001 From: Shubhdeep Singh Date: Fri, 28 Jun 2024 12:35:42 +0530 Subject: [PATCH] Update workflow-features-concepts.md Correct link for know limitations in workflow page Signed-off-by: Shubhdeep Singh --- .../building-blocks/workflow/workflow-features-concepts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-features-concepts.md b/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-features-concepts.md index 186799cb308..efdac157ce6 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-features-concepts.md +++ b/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-features-concepts.md @@ -77,7 +77,7 @@ You can use the following two techniques to write workflows that may need to sch Because workflows are long-running and durable, updating workflow code must be done with extreme care. As discussed in the [workflow determinism]({{< ref "#workflow-determinism-and-code-restraints" >}}) limitation section, workflow code must be deterministic. Updates to workflow code must preserve this determinism if there are any non-completed workflow instances in the system. Otherwise, updates to workflow code can result in runtime failures the next time those workflows execute. -[See known limitations]({{< ref "workflow-features-concepts.md#workflow-determinism-and-code-restraints" >}}) +[See known limitations]({{< ref "#limitations" >}}) ## Workflow activities