Constantly receiving 'This isn't the latest content' prompt on save

[KASCHN]

Has anyone noticed this lately? When I save my flow and it is after the initial save or the second time after a clear cache and hard reload, I get the "this isn't the latest content - your flow was modified by someone else" prompt. There is no one else in my environment and no one else has this flow open. Seems like a cache problem. 

It is problematic because it is two extra clicks to save my flow. And the default radio button is set to 'Discard your changes' which means if you accidentally hit apply you lose your changes whereas it was your original intention to save your changes. Others in my organization have been complaining about this.

[Syrio]

I have the same issue since a couple of days ago, very frustrating.
Do you by any chance use environment variables in the flow and use a devops pipeline to deploy the flow/solution in different environments?

[KASCHN]

We have environmental variables but I am not using them in my flows and yes we do use the devops pipeline to deploy the flow/solution to different environments

[Syrio]

I asked you that because we made some changes in the pipeline and that seemed like the only probable cause for the issue.
But at least for me it seems like it stopped doing it, I still have no clue what caused it and how it fixed itself.

[Syrio]

Never mind, it just started doing it again.

[GDSI]

Chiming in as another pissed off developer. Especially the fact that the default is set to revert. So frustrating.

[Seemorgh]

Add me to the bunch. Such a time waster. I'm pissed off with MS. Why don't their QA staff pick these things up during testing and leave them to frustrated users to discover?

[ell10706]

Chiming in as well. This must not have been tested by folks who edit and test their flows regularly. Whenever I perform an initial test, then go back, make edits, and try to test again, I receive this dialog. I am the only one editing my flows. A page restart fixes this one time, but it reoccurs again immediately. Please turn this off until it's sorted - this is such a time sink.

[VNO]

Same problem here.
Very annoying.

[Anonymous]

Getting the same issue here now

[LimeLeaf]

Had the same problem since yesterday.

Somehow it disappeared this afternoon without any changes on our side.

[VNO]

Seems to be a known bug.

We received this answer:
"It is a known issue and Product Group is looking into it. Until there is a solution, you can try to log out, clear cookies, and log in again to see if it helps."

😕

Kr

[HKICE]

Did you find any resolution to this?  It's Oct 2023 and it's started hapenning to me now !*()@#&)(#$*

[Anonymous]

Thanks for posting this.  This issue just began with a flow of ours that hasn't been modified in 3 months.  Tried saving a copy of the flow but the copy gives us a different issue and keeps erroring on save with the following message: 

The flow is missing a connection for api 'shared_commondataserviceforapps'. Reauthenticate the connection or remove from the flow and re-save.

The error is inaccurate as we tried creating new connections for each Dataverse connector and the error remains.  I'll be opening a case with MS as well because this flow is lengthy and critical to our org.

[sureshmemmi83]

The scenarios you explained happened to me today, I made a load of changes to my Flow and hit save and mistakenly hit Apply forgetting that the default selection is 'Discard your changes' - and lost all my changes, no way to get them back so had to redo them. Couldn't get onto to user voice for some reason so just posting here, if this is an update then it needs to consider this happening as I'm sure I'm not the first.

[eliotcole]

Whilst they're at it they should return the 'Runs history' sidebar when viewing a Logic App run!

(and maybe bring that to PA!)

[VNO]

Same issue here.  It disappeared and start again since a couple of days 😕

[ghman22]

Same issue and share the frustration that it defaults to discard the changes. I saw the Microsoft suggestion for the temporary fix while they work on it, will try that and hope it gets fixed soon.

[margitcurtright]

Where did you find the temporary fix? Can you provide the link?

[ghman22]

Hi margitcurtright, the temporary fix I referred to was from VNO's comment on 5-31-2023 where they referenced a response from Microsoft with the suggestion to try to log out, clear cookies, and log in again to see if it helps.

I don't have a link for this suggestion from Microsoft but you can look at the previous comments in this string to find VNO's comment with this info.