Increase request timeout for Logic apps
Current request timeout is 120 seconds and is non-editable, please make it editable and allow users to increase it till 10 minutes.
Simon Berg commented
Yes! We really need to override the default timeout policy.
I agree with this request.
Sometimes i'm executing Runbooks in Azure Automation with a Logic App and since i'm not in control of the load where i execute my code, 2 min. is not fair as a timeout value.
I would suggest to increase the range to at least 60 minutes or give us an Policy setting so we are able to override the default 2 min. Because it still makes sense to aim for simple and quick requests...
arul mouzhi commented
much needed feedback!
Janne Kujanpää commented
Shorter timeout also should be allowed not only larger.
Ged Harrris commented
I connect to a number of downstream enterprise system which have 2-4 mins timeout. The Request therefore reaches timeout before these system timeouts have been triggered, orphaning the response to an unknown return state.
Is there an update on looking into this as this is causing us a problem when testing a Logic App directly in isolation due to cold starts causing timeouts as opposed to calling it from a parent Logic App (where the 120 second timeout does not seem to apply).
Ben Harris commented
Some APIs we pull from are large and require longer extraction times than 120-seconds. This causes the request to fail if it exceeds the 120-second threshold. The workaround is fairly involved, as it requires multiple smaller requests spliced back together on the client-side. An alternative would be to use Azure Functions, which has a 30-minute threshold...but the whole point of using Logic Apps is to benefit from the codeless UI. Please consider fixing. Thanks!