Merge pull request #312338 from xuehongg/xuehongg5

Clarification on timeouts and how to get around of them.

Author: prmerger-automator[bot]

articles/connectors/connectors-native-reqres.md

@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewers: estfan, azla
 ms.topic: how-to
-ms.date: 06/18/2025
+ms.date: 02/25/2026
 ---
 
 # Receive and respond to inbound HTTPS calls sent to workflows in Azure Logic Apps
@@ -30,7 +30,7 @@ To run your workflow by sending an outgoing or outbound request instead, use the
 
 ## Prerequisites
 
-* An Azure account and subscription. If you don't have a subscription, you can [sign up for a free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
+- An Azure account and subscription. [Get a free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
 
 - The logic app resource with the workflow where you want to receive the inbound HTTPS request.
 
@@ -373,9 +373,10 @@ Now, continue building your workflow by adding another action as the next step.
 > [!NOTE]
 >
 > Your workflow keeps an inbound request open only for a [limited time](../logic-apps/logic-apps-limits-and-config.md#http-limits). 
-> Assuming that your workflow also includes a Response action, if your workflow doesn't return a response to the caller 
-> after this time expires, your workflow returns the **504 GATEWAY TIMEOUT** status to the caller. If your workflow 
-> doesn't include a Response action, your workflow immediately returns the **202 ACCEPTED** status to the caller.
+> Assuming that your workflow includes a **Response** action with the **Asynchronous response** setting turned off (default), if your workflow 
+> doesn't return a response to the caller within the time limit, your workflow returns the **504 GATEWAY TIMEOUT** status to the caller. 
+> If the **Response** action has the **Asynchronous response** setting turned on, or if your workflow doesn't include a **Response** action, your workflow 
+> immediately returns the **202 ACCEPTED** status to the caller.
 
 For information about security, authentication, and encryption for inbound calls to your workflow, such as [Transport Layer Security (TLS)](https://en.wikipedia.org/wiki/Transport_Layer_Security), [OAuth with Microsoft Entra ID](/entra/architecture/auth-oauth2), [Shared Access Signatures (SAS)](../logic-apps/logic-apps-securing-a-logic-app.md#sas), exposing your logic app resource with Azure API Management, or restricting the IP addresses that originate inbound calls, see [Access for inbound calls to request-based triggers](../logic-apps/logic-apps-securing-a-logic-app.md#secure-inbound-requests).
 

articles/logic-apps/logic-apps-limits-and-config.md

@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: rohithah, laveeshb, rarayudu, azla
 ms.topic: reference
-ms.date: 02/24/2026
+ms.date: 02/25/2026
 ms.custom: sfi-image-nochange
 ---
 
@@ -414,7 +414,7 @@ For Standard logic app resources in single-tenant Azure Logic Apps, stateless wo
 | Name | Multitenant | Single-tenant | Notes |
 |------|-------------|---------------|-------|
 | Outbound request | 120 sec <br>(2 min) | 225 sec <br>(3 min and 45 seconds) <br>(Default) | Examples of outbound requests include calls made by the HTTP trigger or action. If the server doesn't respond within the timeout limit, the HTTP action fails. <br><br>**Tip**: For longer running operations, use an [asynchronous polling pattern](logic-apps-create-api-app.md#async-pattern) or an ["Until" loop](logic-apps-workflow-actions-triggers.md#until-action). To work around timeout limits when you call another workflow that has a [callable endpoint](logic-apps-http-endpoint.md), you can use the built-in Azure Logic Apps action instead, which you can find in the designer's operation picker under **Built-in**. <br><br>To change the default timeout limit in the single-tenant service, follow these steps in the Azure portal or see [Edit host and app settings for logic apps in single-tenant Azure Logic Apps](edit-app-settings-host-settings.md): <br><br>1. On the designer, in the workflow, select the **HTTP** action. <br>2. In the action pane, select the **Settings** tab. <br>3. Under **Request options - Timeout**, change the duration. |
-| Inbound request | 120 sec <br>(2 min) | 225 sec <br>(3 min and 45 seconds) <br>(Default) | Examples of inbound requests include calls received by the Request trigger, HTTP Webhook trigger, and HTTP Webhook action. <br><br>**Note**: For the original caller to get the response, all steps in the response must finish within the limit unless you call another nested workflow. For more information, see [Call, trigger, or nest logic apps](../logic-apps/logic-apps-http-endpoint.md). <br><br>To change the default limit in the single-tenant service, review [Edit host and app settings for logic apps in single-tenant Azure Logic Apps](edit-app-settings-host-settings.md). |
+| Inbound request | 120 sec <br>(2 min) | 225 sec <br>(3 min and 45 seconds) <br>(Default) | Examples of inbound requests include calls received by the **Request** trigger, **HTTP Webhook** trigger, and **HTTP Webhook** action. <br><br>**Note**: For the original caller to get the response when the **Response** action has the **Asynchronous response** setting turned off (default), all steps in the response must finish within the time limit. Otherwise, if the **Response** action has the **Asynchronous response** setting turned on, or if your workflow doesn't include a **Response** action, the call pattern is asynchronous. Your workflow can take whatever time is needed to respond. |
 
 <a name="content-storage-size-limits"></a>