I am trying to understand the "Retry policy" of any action, specifically for the Power BI connector.
I want to improve the times to retry if there is any failure (usually with status 429). When my policy runs, it takes at least 3 minutes or more to execute. However, my users get confused because it appears that the flow didn't trigger.
I tested using 'Exponential interval' and then switched to 'Fixed time,' There is no difference, and there is a maximum of 3 retries.
What are the best settings for this feature? Or is it an expected behavior?
Hey @vsslasd
So my scenario is a little different, I have some custom APIs running , so they work in 1st go only. So, I have set up retry policy to none to get the best performance. But in your case you can change it to fixed intervals of like 1 minute each.
By default its 3 minutes and you have also written above it executes in more than 3 minutes.
So what happens is, if it fails on the 1st attempt, retry will happen 3 minutes later, and if it again fails it will happen 2 more times. So, in total 4 times.
So my best option for you would be to keep it fixed intervals of 1 minute, so that if it fails on the first try , after 1 minute it will try for 2nd time and if it fails again it will try after 1 minute for the 3rd time.
And you can keep your custom count as well, for how many times it should retry.
I hope this helps 🙂