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/logic-apps-diagnosing-failures.md
+19-1Lines changed: 19 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: logic-apps
5
5
ms.suite: integration
6
6
ms.reviewer: estfan, azla
7
7
ms.topic: how-to
8
-
ms.date: 08/20/2022
8
+
ms.date: 09/02/2022
9
9
---
10
10
11
11
# Troubleshoot and diagnose workflow failures in Azure Logic Apps
@@ -128,6 +128,24 @@ To help with debugging, you can add diagnostic steps to a logic app workflow, al
128
128
129
129
1. To review how Azure Logic Apps generates and forms a request, run the logic app workflow. You can then revisit the Webhook Tester site for more information.
130
130
131
+
## Performance - frequently asked questions (FAQ)
132
+
133
+
### Why is the workflow run duration longer than the sum of all the workflow action durations?
134
+
135
+
Scheduling overhead exists when running actions, while waiting time between actions can happen due to backend system load. A workflow run duration includes these scheduling times and waiting times along with the sum of all of the action durations.
136
+
137
+
### Usually, my workflow completes within 10 seconds. But, sometimes, completion can take much longer. How can I make sure the workflow always finishes within 10 seconds?
138
+
139
+
* No SLA guarantee exists on latency.
140
+
141
+
* Consumption workflows run on multi-tenant Azure Logic Apps, so other customers' workloads might negatively affect your workflow's performance.
142
+
143
+
* For more predictable performance, you might consider creating [Standard workflows](single-tenant-overview-compare.md), which run in single-tenant Azure Logic Apps. You'll have more control to scale up or out to improve performance.
144
+
145
+
### My action times out after 2 minutes. How can I increase the timeout value?
146
+
147
+
The action timeout value can't be changed and is fixed at 2 minutes. If you're using the HTTP action, and you own the service called by the HTTP action, you can change your service to avoid the 2-minute timeout by using the asynchronous pattern. For more information, review [Perform long-running tasks with the polling action pattern](logic-apps-create-api-app.md#perform-long-running-tasks-with-the-polling-action-pattern).
148
+
131
149
## Common problems - Standard logic apps
132
150
133
151
### Inaccessible artifacts in Azure storage account
0 commit comments