| Ijlal Monawwar

Power Automate Retry and Timeout Policy

Whenever we are creating a flow, we might have encountered that a connector keeps sporadically failing due to some request issues or server-side errors in which the server fails to fulfil an apparently valid request. We can fortunately tackle these issues by setting up the retry policy for the connector. A retry policy applies to intermittent failures, characterized as HTTP status codes 408, 429, and 5xx, in addition to any connectivity exceptions. The default is an exponential interval policy set to retry 4 times. It is a good practice to set a retry policy for sending http requests and for Create, Update, Delete actions for Dataverse or any other service like SharePoint or SQL.

Error Code

Description

408

Request Timeout

429

Too many requests

5xx

500 – Internal Server Error

503 – Service Unavailable

522 – Connection timed out, etc.

For demonstration, I’ll configure a flow for creating a record in Dataverse and set the connectors retry policy.

power automate retry

Click on the three dots menu of the action and select Settings.

power automate retry

We see a retry policy setting which is set to Default.

power automate retry

Here is a table listing all the settings and their descriptions.

Retry Policy

Description

Default

The default is an exponential interval policy set to retry 4 times.

None

Do not retry if failed.

Fixed Interval

Count - Number of times to retry.

Interval - Time between retries.

Exponential Interval

Count - Number of times to retry

Interval - Time between retries

Minimum and Maximum Interval - the retry will happen exponentially (Increase or decrease) between the specified intervals.

In fixed interval policy, we must specify Count, which is the number of retries before failing the flow and Interval, specified in ISO 8601 format, which requires us to set the time between retries, e.g.: PT20S means 20 seconds, PT5H means 5 hours, etc.

power automate retry

In exponential interval policy, we must specify Count, which is the number of retries before failing the flow and Interval, specified in ISO 8601 format, which requires us to set the time between retries, e.g.: PT20S means 20 seconds, PT5H means 5 hours, etc. Minimum and Maximum Interval - the retry will happen exponentially (Increase or decrease) between the specified intervals. If Interval is PT1H and minimum Interval is set to PT1M - it will decrease exponentially till it reaches 1M. Conversely, If Interval is PT1H and maximum Interval is set to PT10H - it will increase exponentially (1-2-4-8-10) till it reaches 10H.

power automate retry

Join us next time, as we continue our journey of learning canvas apps.Click here to learn more about Imperium's Power Apps Services. We hope this information was useful, and we look forward to sharing more insights into the Power Platform world.



About The Blog

Stay updated with what is happening in the Microsoft Business Applications world and initiatives Imperium is taking to ease digital transformation for customers.


More About Us

We provide guidance and strategic oversight to C-Suite and IT Directors for on-going implementations. Feel free to give us a call.

1 331 250 27 17
Send A Message

Ready to Start?

Get a personalized consultation for your project.

Book a Meeting