Disconnected flows after solution import issue

[fmenjivar]

In powerapps, I've created a solution and within the solution there is an application and some automated flows, the automated flows are using a database connection (through connection references).

After the solution is exported (managed or unmanaged) and then imported into another environment, connection references are updated accordingly.

After importing the solution the application is not working as expected because all the automated flows are shown as "not connected". (workflows are turned on but I open the powerapps application and navigate to the flows option, all the flows are shown as "not connected", if I hit the refresh option, the workflows will be connected and the application will perform as expected).

Is there any option to get the automated flows that use connection references "connected" automatically after importing the solution?

[Pstork1]

Did you build the flows originally inside the solution or did you import them?  This sounds like what happens when you import the flows and don't successfully swap them to valid Connection References.  You also have to set the Run Only user setting of the connections when using Connection references.

[fmenjivar]

1. Flows were created inside the solution. (Using the New->Automation->Cloud flow->Instant option that is there in the solutions menu)
2. Flows are tied to connection references, actually after the solution is imported, just hitting the refresh option solves the issue (without changing nor updating anything). Just looking the options to get the solution imported "ready to run" without having to navigate to flows to hit the refresh action.

[Pstork1]

Did you check the settings for the Run Only users?  That normally defaults to the user triggering the flow since this is a Power App triggered flow. That setting needs to be changed to continue using the connection of the flow maker.

[fmenjivar]

Hi

Well I don't see the "run only" option, but I found the root cause of this and now its fixed.

By some reason, the application had a ref to a connection reference that was outside of the solution. (Not clear how the application was referencing a connection reference that was outside of the solution, even the "not connected" flows were using another connection reference that was included in the solution). Anyway, I found it when looking at the application references..

After adding the connection reference that was outside of the solution (it was only in the default solution) the flows were imported with the "connected" status.

Regards,

Freddy

[Pstork1 · Accepted solution]

When you look at the connection references from the ellipses menu of an action it shows all the Connection references in any solution in that environment.  So its pretty easy to pick the wrong one.

[Shivani_PowerAp]

Hi, I just resolved this similar issue by "turning On" the flows listed under my managed solution in the imported environment. Once done, publish the customizations. This will solve the issue. 

[InfinityAlarm]

Just wanted to add that this was very helpful to me! I was getting ready to post asking about this, but then found this one. My problem was that I'd built the flows outside the Solution. Making new versions inside the solution fixed the problem for me!