Skip to content

Commit d2b841e

Browse files
authored
Wording tweaks
1 parent 415f333 commit d2b841e

File tree

1 file changed

+2
-2
lines changed
  • articles/logic-apps/connectors

1 file changed

+2
-2
lines changed

articles/logic-apps/connectors/sap.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -84,9 +84,9 @@ The SAP built-in connector significantly differs from the SAP managed connector
8484

8585
* A longer time-out compared to the SAP managed connector.
8686

87-
The SAP built-in connector runs on the Azure Logic Apps runtime, not the shared or global connector infrastructure in Azure. This behavior means that you can change the default time-out value on the Standard logic app resource by using the **host.json** settings named [**Runtime.FlowRunRetryableActionJobCallback.ActionJobExecutionTimeout**](/azure/logic-apps/edit-app-settings-host-settings?tabs=azure-portal#run-actions) and [**functionTimeout**](/azure/logic-apps/edit-app-settings-host-settings?tabs=azure-portal#run-actions).
87+
The SAP built-in connector natively runs on the Azure Logic Apps runtime, unlike the SAP managed connector that runs on the shared, global, multitenant Azure infrastructure. This design difference means that you can change the default time-out value on the Standard logic app resource by using the **host.json** settings named [**Runtime.FlowRunRetryableActionJobCallback.ActionJobExecutionTimeout**](/azure/logic-apps/edit-app-settings-host-settings?tabs=azure-portal#run-actions) and [**functionTimeout**](/azure/logic-apps/edit-app-settings-host-settings?tabs=azure-portal#run-actions).
8888

89-
This capability means that you can use the SAP built-in connector as-is for long-running synchronous requests. Otherwise, these requests have to use the long-running webhook-based request action pattern in the SAP managed connector, which has a much shorter two-minute time-out for synchronous requests.
89+
The capability to adjust the timeout means that you can use the SAP built-in connector as-is to run long synchronous requests. Otherwise, such requests have to use the action pattern for long-running webhook-based requests in the SAP managed connector, which has a much shorter two-minute time-out for synchronous requests.
9090

9191
* By default, the SAP built-in connector operations are *stateless*. However, you can [enable stateful mode (affinity) for these operations](../../connectors/enable-stateful-affinity-built-in-connectors.md).
9292

0 commit comments

Comments
 (0)