cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Is it possible to increase HTTP connector timeout

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 ?

 

Annotation 2019-11-13 110256.gif

 

Thank you!

 

15 REPLIES 15
Anonymous
Not applicable

@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

 

2019-11-13_0842.png

 

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

 

Sam

@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
Not applicable

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!

 

 

@AnonymousWhat stack are you using to build your API?

Anonymous
Not applicable

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

@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 👍

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
Community Champion
Community Champion

@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.

 

1.png

 

 

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.

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:

FollowTheLion_0-1644712741660.png

FollowTheLion_1-1644712791972.png

Long flow:

FollowTheLion_2-1644712858259.png

 

FollowTheLion_3-1644712877931.png

 

 

 

 

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!

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

 

 

 

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

 

claudiagrajeda_0-1704325679828.png

 

It doesn't alter the request timeout, is there any way to change the request timeout for a single request, we have APIs returning data which huge and it takes at least 10 minutes to complete the processing

I am getting error changing the timeout:

 

MehdiJ007_0-1716997038622.png

Any help suggestion

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (2,320)