Yes he is correct, HOWEVER, this is not a solution. As per usual working with msft the tech is typically (TYPICALLY/ALWAYS) incomplete or full of holes or bugs and it's left to users to come up with workarounds and hacks. That is not a solution.
This platform, now almost 2023 is STILL wrought with these issues. Try adding a field to a list as a test, include some kind of a get items update item action. Great, works. Go back to the list, remove the test field, return to your flow and try and edit it, save it. Sometimes you may simply re-add that action, several times if your flow requires it, then try and save the flow. Good luck. Hmm maybe I'll just delete the problematic action(S). BUZZER nope. No response. Use the technique here: close off the flow, you have no choice but to abandon your changes, go back to edit; oooooops, all your changes are gone remember. Are we having fun with this msft rabbit hole? Now you have to delete the problematic action(S), then re-add.
I'd suggest taking a screen shot before you do if it's compilated enough including grabbing the text of your expressions.
The only sound you're going to hear on this from msft is them sneaking away from the table. All you're going to hear is "add the """"IDEA"""" to user voice" because no one ever would've considered this right? What a great idea, no one needs this kind of intuitive, standard, everyday functionality.
That's my rant.
