You’re offline. This is a read only version of the page.
Announcements
I've been working on a flow for several days now. It's part of a solution (always has been).
Last week I could work like this:
Since yesterday, the "Save" button has been replaced by "Safe draft" and I need to publish the flow before Test becomes available, so now I'm forced to:
It's a dev environment, so publishing is not really a problem, it just adds several seconds to my development cycle which add up over time.
Has there been any change to Power Automate in general (I couldn't find useful Release Notes)? Or is there a setting somewhere which influences that behavior?
Update: There is another flow in the same environment which doesn't exhibit this behavior - I can still Save and Test directly without needing to publish? There's not even a publish button in the flow.
If you look at the 'Availability' section of the following article, there is a note that this only applies to solution cloud flows
So I am guessing, if you have a flow residing in the default solution you might not see the publish button (not tested).
Power Automate - Drafts and versioning for cloud flows
Cheers
Simon
Share
Report
All responses (
Answers (
16
