Logic App Standard Execute SQL Timeout

Mike Holdorf 1

We are using Logic App Standard and using the Execute SQL action. We don't have control over the backend SQL and at times, we have requests that may run up to a minute. The Execute SQL query will time out at 30 seconds with a Gateway Timeout.

We have modified the host.json to include the Runtime.ServiceProviders.Sql.QueryExecutionTimeout, but this doesn't have any effect our our query. Everything still times out at 30 seconds. We have also modified our connectionstring to have a longer time out, but this still does not work.

Does the setting Runtime.ServiceProviders.Sql.QueryExecutionTimeout have any impact on our SQL Queries?
How can we make a call to SQL that runs longer that 30 seconds? The Consumption Logic Apps ran longer (I believe this was 110 seconds).

Thanks,
Mike Holdorf
Neudesic

MayankBargali-MSFT 70,141 Reputation points

2022-02-04T11:35:18.143+00:00

@Mike Holdorf Can you share your host.json file content from the portal by following the steps mentioned here.
Mike Holdorf 1 Reputation point

2022-02-04T13:32:47.883+00:00

Here is the host.json file. We have changed the timeout to be multiple options, but every setting results in a 30 second timeout.

{
"version": "2.0",
"extensionBundle": {
"id": "Microsoft.Azure.Functions.ExtensionBundle.Workflows",
"version": "[1.*, 2.0.0)"
},
"extensions":{
"workflow":{
"settings":{
"Runtime.ServiceProviders.Sql.QueryExecutionTimeout":"00:00:50"
}
}
}
}

1 answer

Mike Holdorf 1 Reputation point

2022-02-08T13:45:57.763+00:00

Found that this setting needs to be in the host.json file as Runtime.ServiceProviders.Sql.QueryExecutionTimeout.

This setting must also be in the Configuration for the Logic App. It is not exactly the same though. In the configuration, you must add: ServiceProviders.Sql.QueryExecutionTimeout and specify a time, such as "00:01:00" for 1 minute.

I tested this from 30 seconds up to 3 minutes and it is now working and times out with the Configuration setting. The Microsoft Documentation only has Runtime.ServiceProviders.Sql.QueryExecutionTimeout as the setting, so it is a little tough to find.
Please sign in to rate this answer.
MayankBargali-MSFT 70,141 Reputation points

2022-02-08T14:24:12.107+00:00

@Mike Holdorf Thanks for sharing the resolution. Want to understand if updating the below setting in host.json didn't help you alone and further you need to add the ServiceProviders.Sql.QueryExecutionTimeout setting under the configuration blade on your logic app or I have missed anything. It will be great if you can share the screenshot or other configuration that you have specified to make this work so I can verify if there is any document gap.

{ "version": "2.0", "extensionBundle": { "id": "Microsoft.Azure.Functions.ExtensionBundle", "version": "[1.*, 2.0.0)" }, "extensions": { "workflow": { "settings": { "Runtime.ServiceProviders.Sql.QueryExecutionTimeout": "00:01:00" } } } }

Mike Holdorf 1 Reputation point

2022-02-08T15:20:48.44+00:00

What you stated above is correct. I updated the host.json file with the setting above and added Runtime.ServiceProviders.Sql.QueryExecutionTimeout. This did not change anything and was always timing out at 30 seconds. I did post this question on another site and was told that this 30 second timeout was a bug that was now fixed. You can find this issue here: 460

The comment in this stated that we needed to add an app setting of ServiceProviders.Sql.QueryTimeout. When I added this entry to the configuration, the timeout is now using this value. I started testing with 30 seconds, then incremented up 30 seconds at a time and this worked.

The documentation for the host.json file is here: edit-app-settings-host-settings. It states in the reference for host.json includes Runtime.ServiceProviders.Sql.QueryExecutionTimeout. It does not state that this needs to be in the Configuration or App Settings and it does not show anywhere that this entry needs to be ServiceProviders.Sql.QueryTimeout.

So this took a little bit of time to finally figure out. We need to be clear on where this setting should be modified and we need to ensure that the names are consistent. Here is the setting I used in the configuration:

MayankBargali-MSFT 70,141 Reputation points

2022-02-09T06:43:33.737+00:00

@Mike Holdorf Thanks for sharing the insights. I will work with Abode and will update the document accordingly.

Surya Meda 0 Reputation points

2024-08-30T14:14:21.6866667+00:00

@Mike Holdorf @MayankBargali-MSFT

I am getting Gateway Time out issue even after adding "ServiceProviders.Sql.QueryTimeout" : " 00:05:00" to Configuration Value in Logic App.

Even tried after adding the same in host.json file, but no luck.

Surya Meda 0 Reputation points

2024-09-02T07:13:52.24+00:00

@Mike Holdorf @Mike Holdorf @MayankBargali-MSFT

and I using node version 18
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Logic App Standard Execute SQL Timeout

1 answer

Your answer