When a flow is edited, it is automatically saved and retry-policies are updated to Default

[koener]

We have issues when we edit a flow. Before we do anything the flow is automatically saved and after that Retry-policies of child flows are set to Default.

Does anyone else experience this and/or is this a bug?

[dpatterson_dl]

I've also experienced this. It's actually broken a couple older flows that were running perfectly prior to me clicking the edit button just to see what the flow was doing. It seems like a very significant bug for the flow to save when the user only clicks edit.

[lauren_collins]

I've noticed this too, but only for some of our flows and not others (despite repeated 'just click Edit, but don't make any changes' attempts). Bloody annoying!

[wimkringsapg]

Its now 2023 and we experience the same issue for some of our flows. Anybody now knows how to solve this issue?

[lauren_collins]

Hi @wimkringsapg I had raised this directly with MS (ref # 2305020030003505). The upshot of it is, they're not sure at this stage why this is happening but it has been raised as a bug with MS.

I also raised how annoying it is that there is no easily accessible audit data from within PA to help determine when and what changes were made. There is MS Purview that can at least tell you who had made changes, but is a bit opaque / blunt as far as using it to using it further as an analytic tool (also doesn't help that we don't have access to it, we have to go through our systems team to get an export of data, ugh). If you're interested in MS Purview, here are some resources:

https://learn.microsoft.com/en-us/power-platform/admin/logging-power-automate

https://learn.microsoft.com/en-us/microsoft-365/compliance/audit-log-enable-disable?view=o365-worldw...

...and the link to MS Purview itself: https://compliance.microsoft.com/

So the upshot is:

1) They're looking into the autosave bug and

2) They're looking at better ways to provide PA users with a useful audit data tool

My advice is to raise this directly with MS and en masse referencing my original call 2305020030003505 to pressure MS into providing answers.

Lauren

[wimkringsapg]

Hi Lauren, thx for your answer. I had a short holiday so I could not react earlier.

In the meanwhile a colleague of mine has made a call at Microsoft and last week we got the reaction that it is a known problem and a fix would be rolled out monday 19/6 to the European region. But when we tested on monday we still had the same problem. When contacting Microsoft again we heared that they were very sorry but they had some problems and delayed the rollout for Monday 26/6.

Because there is no known workaround we now have to wait and can't deploy power automates to production. Also after the fix is deployed we have to manually check all our flows for unwanted changes..

Very disappointing....

[IAmIntractable]

This did roll out and for most you should see the erroneous save only one more time for affected flows as the platform corrects the issue and saves. There were three situations that causes this. and the only one I can recall was "Any Flow with a Switch Action"

[wimkringsapg]

Correct, Monday 26/6 the problem was fixed and all flows that had this problem, now worked fine and we didn't see this error anymore.