[CoE Starter Kit - BUG] Admin | Audit Logs | Sync Audit Logs (V2) - Runs for 3+ hours due to retry setting

[mmcaak]

Does this bug already exist in our backlog?

• I have checked and confirm this is a new bug.

Describe the issue

I saw that from 2025-03-21 at approx 11PM the flow "Admin | Audit Logs | Sync Audit Logs (V2)" which is triggered hourly went from a duration:

• From: approx. 7 min.
• To: approx. 3,5 hours

I looked into the flow and found that the "Perform an Unbound Action" - "Get Azure Secret" had a retry of 12 and took over 3,5 hours to "give up":

The setting for the action retry was the "Default":

I can only think that at some point around the time observed MS has made the default retry so that it would try 12 times using a specific timeout between each retry and then then action would try for +3,5 hours...
I modified the solution and set the retry policy to "None" and now my flow finishes after approx. 5-7 min. again and the the hourly trigger makes sense again.

I would like you to change the retry policy for this action in the future release - maybe other flows are affected as well?

Expected Behavior

The flow usually finishes after approx. 5-7 min. and not 3,5 hours

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.48.2

What app or flow are you having the issue with?

Admin | Audit Logs | Sync Audit Logs (V2)

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

Just see the run history for "Admin | Audit Logs | Sync Audit Logs (V2)" to see that the duration increased and then click on the long runnning flows to see that the mentioned action has been retried 12 times before timeout.

Anything else?

No response

[mmcaak]

I can verify today as well, that:

I modified the solution and set the retry policy to "None" and now my flow finishes after approx. 5-7 min. again and the the hourly trigger makes sense again.

[pbattini]

@mmcaak Default policy has been used to handle transient failures, which are temporary issues that can often be resolved by retrying the action : Implement a retry policy

The Default policy supposed to make 4 exponential retries.

• The first retry might occur after 1 minute.
• The second retry after 2 minutes.
• The third retry after 4 minutes, and so on.

It's strange that in your case it retried 12 times. Please log a Power Platform support ticket to understand this behavior.

[pbattini]

@mmcaak We have changed the Policy from Default to Fixed Interval. This will be part of April 2025 release. Please test and provide feedback.