Skip to content

Commit 95a8135

Browse files
Siddharthecfan
andauthored
Apply suggestions from code review
Co-authored-by: Esther Fan <[email protected]>
1 parent 6ee2ee6 commit 95a8135

File tree

1 file changed

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

1 file changed

+3
-3
lines changed

articles/logic-apps/connectors/sap.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -82,11 +82,11 @@ The SAP built-in connector significantly differs from the SAP managed connector
8282

8383
This capability addresses a problem with the SAP managed connector where the outcome from the autocommit behavior is silent and observable only through logs.
8484

85-
* A longer time out compared to the managed connector.
85+
* A longer time-out compared to the managed connector.
8686

87-
The SAP built-in connector runs with 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** setting named [**Runtime.FlowRunRetryableActionJobCallback.ActionJobExecutionTimeout**](/azure/logic-apps/edit-app-settings-host-settings?tabs=azure-portal#run-actions) and the [functionsTimeout host setting](/azure/azure-functions/functions-host-json#functiontimeout). compared to the SAP managed connector where the time-out is two minutes.
87+
The SAP built-in connector runs with 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** setting named [**Runtime.FlowRunRetryableActionJobCallback.ActionJobExecutionTimeout**](/azure/logic-apps/edit-app-settings-host-settings?tabs=azure-portal#run-actions) and the [**functionTimeout** host setting](/azure/logic-apps/edit-app-settings-host-settings?tabs=azure-portal#run-actions).
8888

89-
This capability means that long-running requests can work without you having to manually implement the long-running webhook-based request action pattern.
89+
This capability means that you can use the SAP built-in connector instead, and long-running requests work without having to use the long-running webhook-based request action pattern in the SAP managed connector, which has a two-minute time-out.
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)