Differentiate between Save and Publish

[BrianKennemer]

Right now you cant Save your flow if it contains any required fields. I get why but if you made 'publishing' a two step process like it is in PowerApps it would be very useful. Do this validation on the Publish so that I can drop lots of actions in the right places and still save my Flow. 

[Stephen]

Thank you for the suggestion, this is a great idea.

[Rothrock42]

It looks like there hasn't been much action on this for more than a year. Any progress? It is so annoying to lose work because I can't save a step that isn't quite working yet.

[Tqphan87]

This is so simple but absolutely necessary. If I'm creating/modifying my flow and have to pause/quit midway for whatever reason, I can't save until I "resolve" all the errors. Save/Publish is already avail for PowerApps. 

[Woocon]

Almost 1.5 years ago since any kind of update on this really well needed idea, any updates on this?

Did a small change yesterday on a quite large flow and could not save where I had to spend a good hour in the middle of the night just to be able to save the flow. Would be a life saver to have the ability to be able to save incomplete flows. 😉 🙄

[Martinski]

So frustrating to lose all of my editing because I can't freakin' save my flow when it's not 100% working. Give me a break. That is total BS.

[JRossi]

This feature is a must!  It would be less stressful when you coming to the end of your day and can't save cause of something not correct or missing.  This got my vote!