Skip to content

Commit f3a7d30

Browse files
authored
Reword multiple workflows best practice more generically
1 parent 2997610 commit f3a7d30

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

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

Lines changed: 2 additions & 4 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

0 commit comments

Comments
 (0)