cancel
Showing results for
Did you mean:

## 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!

4 REPLIES 4
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:

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.
Kudo Collector

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

To verify this, I did some testing in Flow.

I made a simple Flow which returns 429 status.

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

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
New Member

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

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

Announcements

#### Celebrating the May Super User of the Month: Laurens Martens

@LaurensM  is an exceptional contributor to the Power Platform Community. Super Users like Laurens inspire others through their example, encouragement, and active participation. We are excited to celebrated Laurens as our Super User of the Month for May 2024.   Consistent Engagement:  He consistently engages with the community by answering forum questions, sharing insights, and providing solutions. Laurens dedication helps other users find answers and overcome challenges.   Community Expertise: As a Super User, Laurens plays a crucial role in maintaining a knowledge sharing environment. Always ensuring a positive experience for everyone.   Leadership: He shares valuable insights on community growth, engagement, and future trends. Their contributions help shape the Power Platform Community.   Congratulations, Laurens Martens, for your outstanding work! Keep inspiring others and making a difference in the community!   Keep up the fantastic work!

#### Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

#### Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!