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/connectors/connectors-native-reqres.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -175,7 +175,7 @@ This built-in trigger creates a manually callable HTTPS endpoint that can receiv
175
175
176
176
For example, you can respond to the request by [adding a Response action](#add-response), which you can use to return a customized response and is described later in this topic.
177
177
178
-
Your logic app keeps the incoming request open only for one minute. Assuming that your logic app workflow includes a Response action, if the logic app doesn't return a response after this time passes, your logic app returns a `504 GATEWAY TIMEOUT` to the caller. Otherwise, if your logic app doesn't include a Response action, your logic app immediately returns a `202 ACCEPTED` response to the caller.
178
+
Your logic app keeps the incoming request open only for a [limited time](../logic-apps/logic-apps-limits-and-config.md#request-limits). Assuming that your logic app workflow includes a Response action, if the logic app doesn't return a response after this time passes, your logic app returns a `504 GATEWAY TIMEOUT` to the caller. Otherwise, if your logic app doesn't include a Response action, your logic app immediately returns a `202 ACCEPTED` response to the caller.
179
179
180
180
1. When you're done, save your logic app. On the designer toolbar, select **Save**.
181
181
@@ -205,7 +205,7 @@ Here's more information about the outputs from the Request trigger:
205
205
206
206
You can use the Response action to respond with a payload (data) to an incoming HTTPS request but only in a logic app that's triggered by an HTTPS request. You can add the Response action at any point in your workflow. For more information about the underlying JSON definition for this trigger, see the [Response action type](../logic-apps/logic-apps-workflow-actions-triggers.md#response-action).
207
207
208
-
Your logic app keeps the incoming request open only for one minute. Assuming that your logic app workflow includes a Response action, if the logic app doesn't return a response after this time passes, your logic app returns a `504 GATEWAY TIMEOUT` to the caller. Otherwise, if your logic app doesn't include a Response action, your logic app immediately returns a `202 ACCEPTED` response to the caller.
208
+
Your logic app keeps the incoming request open only for a [limited time](../logic-apps/logic-apps-limits-and-config.md#request-limits). Assuming that your logic app workflow includes a Response action, if the logic app doesn't return a response after this time passes, your logic app returns a `504 GATEWAY TIMEOUT` to the caller. Otherwise, if your logic app doesn't include a Response action, your logic app immediately returns a `202 ACCEPTED` response to the caller.
209
209
210
210
> [!IMPORTANT]
211
211
> If a Response action includes these headers, Logic Apps removes these headers
@@ -263,4 +263,4 @@ Your logic app keeps the incoming request open only for one minute. Assuming tha
263
263
264
264
## Next steps
265
265
266
-
* [Connectors for Logic Apps](../connectors/apis-list.md)
266
+
* [Connectors for Logic Apps](../connectors/apis-list.md)
0 commit comments