Is it possible to increase HTTP connector timeout

[Anonymous]

Hi,

is it possible to increase timeout for HTTP connector in power Automate?

my api takes more than 120 seconds to respond and HTTP connector default timeout is 120 seconds only i guess so it fails as you can see in image below. can than be done ?

Thank you!

[Anonymous]

@Anonymous 

Hi,

You can do this from the setting page for the HTTP action.

- Click the three dots in the top right corner of the HTTP action

- Click 'settings'

- Enter a value in timeout field, using the ISO 8601 Duration format - https://www.digi.com/resources/documentation/digidocs/90001437-13/reference/r_iso_8601_duration_format.htm

If you found this post helpful then please consider marking it as a solution.

Sam

[Jay-Encodian]

@Anonymous- That setting only applies when the HTTP endpoint you are calling implements the async pattern, i.e. the endpoint will return a 202 accepted response, also adding a header property named 'Location' which should then be polled to check the status of the long running job.

@AnonymousIf your HTTP endpoint exceeds the 120 second limit you should implement the async pattern, just changing the Timeout setting on the action will not work.

Hope this helps

Jay

[Anonymous]

Thank you @Anonymous for the response,

Thank you @Jay-Encodian, can you please pass on little more information on how that can be implemented and any reference referring to async pattern will be helpful!

[Jay-Encodian]

@AnonymousWhat stack are you using to build your API?

[Anonymous]

@Jay-Encodian - we are using ASP.NET & REST to build the API

[Jay-Encodian]

@Anonymous- here you go

https://docs.microsoft.com/en-us/azure/architecture/patterns/async-request-reply

If this provides the info you need please mark as a solution to help others find the info 👍

[FollowTheLion]

I've been using HTTP GET (rather than POST) so that my execution is paused while the subordinate flow I'm calling via GET is executed.  (When I say subordinate flow, I'm talking about my API call to whatever slave process, which in my case is another Power Automate flow, but for you will be whatever API you're calling.)  In my case, I want it to take as long as it takes.  I used @Anonymous's method and I think it's working.  For 30 minutes, I used a value of P0Y0M0DT0H30M0S, which is following the format detailed below.

Alternatively, you could use a POST, which will initiate that process and then continue executing in parallel without waiting, in which case you will need to find a way to poll the status of the subordinate flow (API call) to detect when it either finishes or fails, as @Jay-Encodian suggests.

Here's an excerpt from a site that I found listing the definition for that ISO 8601 duration format:

ISO 8601 duration format

ISO 8601 Durations are expressed using the following format, where (n) is replaced by the value for each of the date and time elements that follow the (n):

P(n)Y(n)M(n)DT(n)H(n)M(n)S

Where:

• P is the duration designator (referred to as "period"), and is always placed at the beginning of the duration.
• Y is the year designator that follows the value for the number of years.
• M is the month designator that follows the value for the number of months.
• W is the week designator that follows the value for the number of weeks.
• D is the day designator that follows the value for the number of days.
• T is the time designator that precedes the time components.
• H is the hour designator that follows the value for the number of hours.
• M is the minute designator that follows the value for the number of minutes.
• S is the second designator that follows the value for the number of seconds.

For example:

P3Y6M4DT12H30M5S

Represents a duration of three years, six months, four days, twelve hours, thirty minutes, and five seconds.

[Jay-Encodian]

@FollowTheLion- The HTTP verb used in the request is irrelevant. For a HTTP request using the action originally stated (regardless or the verb / request method) to exceed the timeout value, the endpoint you are calling has to implement an aysnc pattern... i.e. return a 202 response with a location header. The setting you are referring to only applies for endpoint which implement this pattern... it actually tells you this in the description of the setting.

[FollowTheLion]

You are correct.  Thank you for clarifying.  I discovered that entering a long timeout doesn't work.  I'm going to try this out.  Thanks so much.

[FollowTheLion]

You are correct.  Thank you for clarifying.  I discovered that entering a long timeout doesn't work.

I tried this out.  I set the response code to 202 and set the settings of the response to asynchronous.  That allows me to pick any time I want for a timeout.

These screenshots show how to do it.

I set up a simple http-triggered flow, added a delay of five minutes, and then a response with code 202, with asynchronous checked (based on @Jay-Encodian's instructions).  And I set up a manually triggered flow to call it, and selected the longer timeout and asynchronous pattern (which is on by default).  This now works.

Thanks so much for pointing out my mistake.  My production flow is now working properly.

Calling flow:

Long flow:

[Ricardo_1982]

HI @FollowTheLion 
your solution is amazing! 
I have the same issue with HTTP connector timeout, can you please share us one screenshot from your "when http request is received" trigger, I tried to make it but I dont know how to connect this trigger with my HTTP GET request from another custom flow. (I executed my custom HTTP flow but It was not way to match it with the "Long Flow" that you mencionated. my custom flow is still giving me the timeout and the long flow is not started. 

Thanks a lot!

[bk-006]

@FollowTheLion  how to created the flow can you share the entire flow for reference

[claudiagrajeda]

i am getting an error when i try to change the timeout.   Can anyone help me ?? thanks