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

#### Tuesday Tip: Getting Started with Private Messages & Macros

Welcome to TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   This Week's Tip: Private Messaging & Macros in Power Apps Community   Do you want to enhance your communication in the Community and streamline your interactions? One of the best ways to do this is to ensure you are using Private Messaging--and the ever-handy macros that are available to you as a Community member!   Our Knowledge Base article about private messaging and macros is the best place to find out more. Check it out today and discover some key tips and tricks when it comes to messages and macros:   Private Messaging: Learn how to enable private messages in your community profile and ensure you’re connected with other community membersMacros Explained: Discover the convenience of macros—prewritten text snippets that save time when posting in forums or sending private messagesCreating Macros: Follow simple steps to create your own macros for efficient communication within the Power Apps CommunityUsage Guide: Understand how to apply macros in posts and private messages, enhancing your interaction with the Community For detailed instructions and more information, visit the full page in your community today:Power Apps: Enabling Private Messaging & How to Use Macros (Power Apps)Power Automate: Enabling Private Messaging & How to Use Macros (Power Automate)  Copilot Studio: Enabling Private Messaging &How to Use Macros (Copilot Studio) Power Pages: Enabling Private Messaging & How to Use Macros (Power Pages)

#### Exclusive LIVE Community Event: Power Apps Copilot Coffee Chat with Copilot Studio Product Team

We have closed kudos on this post at this time. Thank you to everyone who kudo'ed their RSVP--your invitations are coming soon!  Miss the window to RSVP? Don't worry--you can catch the recording of the meeting this week in the Community.  Details coming soon!   *****   It's time for the SECOND Power Apps Copilot Coffee Chat featuring the Copilot Studio product team, which will be held LIVE on April 3, 2024 at 9:30 AM Pacific Daylight Time (PDT).     This is an incredible opportunity to connect with members of the Copilot Studio product team and ask them anything about Copilot Studio. We'll share our special guests with you shortly--but we want to encourage to mark your calendars now because you will not want to miss the conversation.   This live event will give you the unique opportunity to learn more about Copilot Studio plans, where we’ll focus, and get insight into upcoming features. We’re looking forward to hearing from the community, so bring your questions!   TO GET ACCESS TO THIS EXCLUSIVE AMA: Kudo this post to reserve your spot! Reserve your spot now by kudoing this post.  Reservations will be prioritized on when your kudo for the post comes through, so don't wait! Click that "kudo button" today.   Invitations will be sent on April 2nd.Users posting Kudos after April 2nd at 9AM PDT may not receive an invitation but will be able to view the session online after conclusion of the event. Give your "kudo" today and mark your calendars for April 3, 2024 at 9:30 AM PDT and join us for an engaging and informative session!