An Azure service that automates the access and use of data across clouds without writing code.
No. A 15-minute timeout is not supported for a built-in HTTP action in a Standard Logic App.
For Standard logic apps, the built-in HTTP action uses Runtime.Backend.HttpOperation.RequestTimeout, and the default value is 00:03:45. That value is also the maximum value.
If the call is a managed API connector action, Runtime.Backend.ApiConnectionOperation.RequestTimeout is 00:02:00.
If the action is timing out because the target service takes a long time to finish, the supported approach is to change the called service to use the asynchronous pattern instead of waiting on a long synchronous response. The Logic Apps troubleshooting guidance also states that action timeout for the HTTP action is fixed at 2 minutes in that scenario and recommends the polling action pattern for long-running tasks.
If this workflow must handle long-running work, a better fit can be:
- Return immediately from the target endpoint.
- Continue processing asynchronously.
- Have Logic Apps poll for completion, using the async request-reply pattern.
host.json timeout settings that can be increased apply to some other operation types, such as function-based built-in operations, but not to extend the built-in HTTP action to 15 minutes.