cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Frequent Visitor

Error "Cannot start unpublished flow. Authenticate the flow connections and resave the flow to activate." after importing a flow

I built a flow inside a solution and everything is working as expected.  I export the solution and then re-import the solution into the same environment.  Now the flow is disabled.   If I try to enable it I get the message
         "Cannot start unpublished flow. Authenticate the flow connections and resave the flow to activate."
Even thou the connection for the flow shows a green checkmark.   The only why I can get it running again is to edit the flow and go into each action that uses the connection (don't have to change anything just look at it) then I can save and enable the flow.
 
a) this doesn't seem right, why can't I just enable the flow
b) is there a way to automate this process (eg deployment from DevOps build)
1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Frequent Visitor

When you build a flow from a solution you need to pick the 'Common Data Service (Current Environment)' connector.  Do NOT pick 'Common Data Service' connector. 

 

These are two different connectors and they behave completely differently.   The former will allow you to import without having to re-authentication and status of the flow will be 'On'.  

 

NOTE: 'Common Data Service' does let you set the Environment to '(Current)'  don't be fooled by this, you will still need to re-authentication the actions that use this after an solution import.

 

NOTE:  the trigger for the 'Common Data Service (Current Environment)' connector is a bit flaky if you edit the flow, toggling the scope normally fixed it for me.

 

View solution in original post

2 REPLIES 2
Highlighted
Dual Super User III
Dual Super User III

Hey @aggggg1 

 

This is the expected behavior for flow exported as a part of a solution or exported individually too. 

 

In the ones that are exported individually, you just have to provide the connections at the beginning. But the ones that are a part of a solution needs to have the connections updated on the actions itself. 

 

Currently there is no way to automate this process (automating deployment from a devops build has been recently added for entire solutions in PowerApps but there is too less you can do about the connections)

 

You can try creating an idea post or upvote already existing similar ones in regard to this over  here: https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas

 

Hope this Helps!

 

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

 

 

Highlighted
Frequent Visitor

When you build a flow from a solution you need to pick the 'Common Data Service (Current Environment)' connector.  Do NOT pick 'Common Data Service' connector. 

 

These are two different connectors and they behave completely differently.   The former will allow you to import without having to re-authentication and status of the flow will be 'On'.  

 

NOTE: 'Common Data Service' does let you set the Environment to '(Current)'  don't be fooled by this, you will still need to re-authentication the actions that use this after an solution import.

 

NOTE:  the trigger for the 'Common Data Service (Current Environment)' connector is a bit flaky if you edit the flow, toggling the scope normally fixed it for me.

 

View solution in original post

Helpful resources

Announcements
Community Conference

Power Platform Community Conference

Check out the on demand sessions that are available now!

Power Platform ISV Studio

Power Platform ISV Studio

ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.

Top Kudoed Authors
Users online (10,398)