You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/logic-apps/create-single-tenant-workflows-azure-portal.md
+3-5Lines changed: 3 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ ms.suite: integration
7
7
ms.reviewer: estfan, azla
8
8
ms.collection: ce-skilling-ai-copilot
9
9
ms.topic: how-to
10
-
ms.date: 10/26/2024
10
+
ms.date: 01/21/2025
11
11
# 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.
12
12
---
13
13
@@ -91,9 +91,7 @@ For optimal designer responsiveness and performance, review and follow these gui
91
91
92
92
- Consider splitting business logic into multiple workflows where necessary.
93
93
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).
97
95
98
96
<aname="create-logic-app-resource"></a>
99
97
@@ -153,7 +151,7 @@ More workflows in your logic app raise the risk of longer load times, which nega
153
151
> be **workflowApp**. However, in some scenarios, this app setting might be missing, for example,
154
152
> due to automation using Azure Resource Manager templates or other scenarios where the setting
155
153
> 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**.
157
155
> For more information, see the [**APP_KIND** app setting](edit-app-settings-host-settings.md#reference-local-settings-json).
0 commit comments