Often times, There could be an issue where your HTTP request isn’t hitting well. So, to overcome this, you might want your Flow to Retry after a certain duration and for some number of times.

You want to setup a Retry policy for the same. Here’s how you do it!

Setting Retry Policy

Follow this to setup a Retry Policy of your Flow

1. Locate your HTTP step and navigate to Settings
   




2. Once you’re in Settings pane, scroll below and look for Retry Policy.
   




3. Default type is set by default, if you expand it, you can select what should be the Retry Type. In  this example, I’ve set to Fixed Interval for simplicity
   Default is set to 4 retries at an exponential interval. (Exponential increment type is a little confusing to explain, you can check this post as users discuss how exponential time increments work – )
4. In Fixed Interval type, I’ve set number of retry count to be 3 and duration between each retry should be 30 seconds (represented in ISO-8601 format)
   
5. With that, the policy is set. And the HTTP request step will try for 3 times at the interval of 30 seconds each.

 

If you want to test using some HTTP request, you can sample HTTP requests from here – https://httpstat.us/

How it works

Look for Failed Runs to see the result –

1. Open a Failed Run where you know HTTP request could have failed
   
2. Now, look for your HTTP request where you set the policy on. Expand the same.
   
3. Upon expanding, you can see that there were 3 retries and it failed due to a timeout i.e. 408
   
4. You can also check on the right hand side of the page which says that the total duration of all these retries were 1 min 30 seconds
   

If you observe the Flow Runs, you can find the the Flow did consistently try to run at an interval for the number of times specified.

In case you’re looking for more Flow/Power Automate related posts, check below –

1. Make HTTP request from Flow in Power Automate
2. Using Parse JSON to read individual List Records in Flow|Power Automate
3. Selecting (Current) in Environment in Power Automate CDS connector and why it matters
4. Retrieve only active Dynamics 365 CE licensed Users in CDS connector in Power Automate
5. Secure Input/Output in Power Automate Run History
6. Approval Process using Power Automate
7. Create a To-Do List Item of Important Outlook Emails using Power Automate
8. RSS notifications to your phone using Power Automate
9. Enable Flow button on D365 Ribbon
10. Button Flow in Power Automate to replicate a Quick Create Form in D365 CE

Hope this helps!!