Skip to content

Commit a1cf4a1

Browse files
Merge pull request #293327 from ecfan/patch-1
Reword multiple workflows best practice more generically
2 parents e5936a9 + a084298 commit a1cf4a1

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

articles/logic-apps/create-single-tenant-workflows-azure-portal.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.suite: integration
77
ms.reviewer: estfan, azla
88
ms.collection: ce-skilling-ai-copilot
99
ms.topic: how-to
10-
ms.date: 10/26/2024
10+
ms.date: 01/21/2025
1111
# Customer intent: As a developer, I want to create my first example Standard logic app workflow that runs in single-tenant Azure Logic Apps using the Azure portal.
1212
---
1313

@@ -91,9 +91,7 @@ For optimal designer responsiveness and performance, review and follow these gui
9191

9292
- Consider splitting business logic into multiple workflows where necessary.
9393

94-
- Have no more than 10-15 workflows per logic app resource.
95-
96-
More workflows in your logic app raise the risk of longer load times, which negatively affect performance. If you have mission-critical logic apps that require zero downtime deployments, consider [setting up deployment slots](set-up-deployment-slots.md).
94+
- When you add more workflows to your logic app resource, you increase cold start times and the risk for longer load times, which negatively affect performance. To reduce these risks or if you have mission-critical logic apps that require zero downtime deployments, [set up deployment slots](set-up-deployment-slots.md).
9795

9896
<a name="create-logic-app-resource"></a>
9997

@@ -153,7 +151,7 @@ More workflows in your logic app raise the risk of longer load times, which nega
153151
> be **workflowApp**. However, in some scenarios, this app setting might be missing, for example,
154152
> due to automation using Azure Resource Manager templates or other scenarios where the setting
155153
> isn't included. If certain actions don't work, such as the **Execute JavaScript Code** action,
156-
> or if the workflow stops working, check that the **APP_KIND** app setting exists and is set to to **workflowApp**.
154+
> or if the workflow stops working, check that the **APP_KIND** app setting exists and is set to **workflowApp**.
157155
> For more information, see the [**APP_KIND** app setting](edit-app-settings-host-settings.md#reference-local-settings-json).
158156
159157
1. When you finish, select **Next: Storage**.

0 commit comments

Comments
 (0)