cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Retry Policy Exponential Interval Explanation

Hello,

 

I am trying to setup exponential interval retry policy for insert function into google sheets but cannot find good explanation on how it works. I set count to maximum possible 90 and it is clear to me that it will try 90 times. Confusion comes from "Interval", "Minimum Interval", and "Maximum Interval" options. Since I am on Flow 2 plan meaning that my flows run once per minute, I will enter "PT1M" into "Interval" Field. Then I will enter "PT1H" into "Maximum Interval" field. To me, that means that first retry will happen in 1 minutes, and intervals of all subsequent retries will keep increasing exponentially until they hit 1 hour. Then, retries will happen once per hour until all 90 retries are done. Let me know if my logic correct, because I cannot find explanation anywhere.

Also, why do I need "Minimum Interval"? Does it mean that I can use "Minimum Interval" instead of "Maximum Interval"? I assume if I enter "PT1H" into "Interval" and then "PT1M" into "Minimum Interval", then the first retry will occur after 1 hour and all subsequent retries will keep exponentially decreasing until retries happen every minute and until they hit count of 90?

 

Thanks!MS Flow Exponential Retry.JPG

4 REPLIES 4
v-yamao-msft
Community Support
Community Support

HI @abeguliev ,

 

The default retry attempts is 4 times. However, we could configure the retry policy depends on our scenario.

 

What you were saying on the Minimum interval and maximum interval is correct.

 

Please also check the following blog for a reference:

https://veenstra.me.uk/2018/08/03/microsoft-flow-protect-your-sharepoint-flows-from-overload-better/

 

By the way, you also need to follow the limits on Retry policy:

https://docs.microsoft.com/en-us/flow/limits-and-config

 

Best regards,

Mabel

 

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

@abeguliev, setting a minimum will not cause the deltas to exponentially decrease. The min/max are just boundaries to the retry delta, which is determined primarily from the required "interval" field and the retry number. If you omit a max but provide a min, then the max interval range will just be determined by the algorithm's normal behavior.

 

---

I found this post while searching for the same explanation about the peculiar exponential retry options (still with no clear documentation linked from Flow). The only reply was ambiguous on the behvior of the minimum interval, so I did my own research and testing. Since this is the top hit on Google for "microsoft flow exponential retry" and I expect others will find their way here looking for answers, I'll post my findings.

 

First off, it looks like the feature was added in response this request in Logic Apps. Here's the Azure Logic Apps explanation of the implemented feature. It explains the exponential retry policy as "a random interval selected from an exponentially growing range before sending the next request."

 

Since Flow is executed on Logic Apps, I believe the documentaiton for Logic Apps applies to Flow. Here's a screenshot showing how the Flow Action retry settings map to the Logic Apps documentation:

 

2019-10-22 09_22_13-Window.png

 

To verify this, I did some testing in Flow.

 

I made a simple Flow which returns 429 status.

 

2019-10-22 09_25_59-Window.png

 

Then triggered it with varying retry settings and retry-after headers.

 

2019-10-22 09_28_04-Window.png

 

Here are the results:

 

  • "none" retry policy
    • no retries
    • action fails immediately
  • "fixed" retry policy
    • retries at equal intervals based on "count" setting
    • interval is the greater value of the action's "interval" policy or the "retry-after" response header
    • tests
      • interval=PT5S, retry-after=10, intervals were roughly 10s
      • interval=PT15S, retry-after=5, intervals were roughly 15s
  • "exponential" retry policy
    • retries at randomly chosen intervals within an exponentially increasing range
    • see Logic Apps exponential interval retry policy explanation
    •  tests
      • interval=PT5S, retry-after=1, retry deltas were 6/9/15
      • interval=PT5S, retry-after=2, retry deltas were 6/6/12 and 6/10/15
      • interval=PT5S, retry-after=4, retry deltas were 5/9/11
      • interval=PT5S, retry-after=10, retry deltas were 11/10/17
      • interval=PT5S, maximum=PT10S, retry-after=1, retry deltas were 5/10/10
      • interval=PT10S, minimum=PT5S, retry-after=1, retry deltas were 6/20/21
      • interval=PT10S, minimum=PT10S, retry-after=1, retry deltas were 11/18/33

When request fails or times out with error code 429, 408 and 5xx response, then in case of exponential interval, it increases the waiting time between retries after each retry failure and this can be achieved by specifying maximum and minimum interval waiting time. For example: When request fails the first time, it retries after 2 seconds. If it fails again then it waits for 4 seconds before next retry. If it again fails then it waits for another 8 seconds before sending the next request and so on. After each failure it incrementally increases the wait time between the successive retry requests and it keeps retrying and keeps increasing the delay time till the maximum retry count is hit. Therefore it helps the service to reduce the load by giving some rest period for processing all the requests. If the request is failing even after maximum retries, then you will get time out or service unavailable error from the service you are calling.

You can refer to this blog : 

https://medium.com/@pooja41bhardwaj/configure-retry-policy-to-resolve-rate-limit-exceeded-429-error-...

 

Hope this is helpful!

Nuchem
Advocate II
Advocate II

Funny how despite all the technical jargon they used, the last reply, above mine, was the easiest for me to understand. First explain it in single language.. 👍 Thanks @PoojaBhardwaj 

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 (1,100)