Values Disappearing From Flow

[N-Lekim]

Is anyone else running into the problem of values disappearing from their flows?

In the screenshot below, all empty 'Choose a value' fields had previously been filled in.

I came back to work on the flow and found them empty.

This is not the first time this has happened and with no other changes to the flow being made.

This time it was the values on the left, but I have also found instances where previously populated 'true' or 'false' values have gone missing.

Is this a bug in Power Automate?

Any information is greatly appreciated.

Thanks,

-Mike-

[Pstork1]

Did you make any edits to the flow before discovering this?  Making changes to actions that provide the dynamic content for these entries can make them disappear.  I've seen that happen frequently, but I've never seen them disappear for no reason.

[N-Lekim]

I have been making edits in other parts of the flow, but nothing related to the values that disappeared.

I have a couple of parallel branches. I had finished working on/testing the branch in question and it had been working fine. The most recent updates were in other branches. The actions this particular example relies on have not been touched.

Also, this would not explain previous experiences I have had with the 'true'/'false' values disappearing as well.

[kwahmhof]

Did you ever find a solution to this? I am having the same issue.

[N-Lekim]

No. It still happens on occasion. The only possible cause suggested was that I had made changes to the flow which had cascading effects and cleared out the fields. I could believe this explanation if I had been working in the same part of the flow, but there have been times when a flow simply quits working as expected. When I dig in I occasionally find empty fields, even when there were no updates immediately prior to the failures. Not much help, I know, but I've just learned to deal with it.

[YingK]

I also had this issue several times, and it's really frustrating...

When I found them disappeared, I would open up another tab and check, if they were there and I hadn't made too many changes, I would start again. But if you have saved the flow after they're gone, they're gone forever.

This April I even had one change made last year being reverted back automatically. It's a quite stable flow and there's no reason I would have touched it.

I meet this issue again today, and this time my flow is more complicated and I have to redo so many things...

So far, it only happens to "Condtion" action in my experience.

[N-Lekim]

Yes, Very Frustrating!

It still happens to me. I was building new flows the other day and had run through some testing. Everything was working when I clocked out for the day. By the time I got back to it a day or two later, tests were no longer working. I dug into it and found empty fields in a few of my Conditions.

I would really like to know why this happens. It can really make troubleshooting a maddening experience!

[jbruce87]

I have experienced similar issues, and like you they are only within conditions. I have confirmed flow functionality with testing, made no changes to the flow after and attempted to run it the next morning while presenting my proof of concept for the flow and it failed. I dug into it and the Conditions were all blank. I made the required changes, saved it and it worked fine. the problem is this will be an automated flow, if the conditions are wiped at random I can not rely on it and its no longer going to be a viable solution. We need more information as to why this is happening so we can attempt to avoid it! 

[LynetteJH]

This happens to me occasionally as well and did again today.  Have a flow for reimbursement to executives that was working fine.  Suddenly I get notified that the exec received a rejected email when the item had actually been approved.  Looked at the flow, and the condition for Outcome=Approve was missing the Outcome field so it was always going to the rejected side.  Awesome.  That's what I want to happen to executives using this process.  This needs to be looked into.  How can I feel confident using Power Automate if the flow is going to randomly do this?

[Lawnstone]

Been having the same issue here. New to power automate, been working on a flow with a lot moving parts over the past month. It's always in the conditional that values go missing. In some cases absolutely I have changed dynamic content further up the flow which makes sense. But in other cases the comparison value is a literal string that is just gone.

[AmyHw]

This has happened to me on flows that were working fine and that I haven't touched for months. So it's not because of me saving/making changes. It's always the value on the left side of the condition that disappears.

[Lawnstone]

Second day in a row this has happened on the same conditional so I'll provide a little more detail. I'm automating creation of user accounts. I have a list of licenses with display names, codes and GUIDs. I've set the one of those list items to "No license", "null" and "null". So in my conditional where I check if we need a license I check if the GUID is the literal string "null". Perhaps that's a special case and I should use some other string but I've had no runtime errors and I have checked the comparison value is still there after saving.

[Lawnstone]

Disregard that. This is a different case. Literal string "null" is automatically converted to an empty string. Can't even find a way to successfully compare it so I'm just going to change it. That said, I have previously had the exact same issue as LynetteJH where my outcome comparison disappeared as well.

[JurSap82]

I also ran into this problem several times, it is quite frustrating. Hopefully this will be solved soon..

[kylemb350]

Bumping this up in 2024. Having a Case value deleted after I make any other change to the flow. The same happens with a set variable step. I cannot save the flow after adding values as they disappear.

This stemmed from moving a For Each loop over into another case branch. I tried to recreate a new branch and a new variable assignment step, but it seems the whole flow is bugged unfortunately.

[Jim-D]

I'm trying to learn Power Automate and ran into this issue.   In one very simply Flow and I have two steps where this issue pops up.  The first is an Initialize step.  I am defining a loop counter and trying to set it to zero.  When I save the flow and go back into it, the zero (0) is gone.

The second step is a condition test - it compares the result of a function to zero (0).  Same as above, when I save it and go back into the flow, the zero is gone.

This has happened consistently.  And what's funny is I have other variables that I initialize to non-zero values, those never have to be re-entered.