Cannot bind Power App to flows after migrate to another environment

[Colchester]

I have a canvas App with several app trigger flows in DEV environment.

The App is packed in a unmanaged solution and import to UAT env. The flows are moved with export/import method to UAT env.

However, when I edit the App in UAT environment. Select the button, click "Action", I cannot see any flow available. I have checked those migrated flows are actived.

[Pstork1]

If you are going to move the app using a solution then the flows should be included in that solution also.  Otherwise, as you have seen the app in the solution won't be able to see the flows stored in my Flows.  I assume you created the app first and then added it to a solution in the Dev environment?  That would explain why the flows were originally visible.

[Colchester]

Yes, you're right. The solution is created after the App is built. So I have no way to workaround it?

I have to either (1) recreate the App and flow in Solution start from scratch; or (2) recreate the App triggered flows in UAT?

[Colchester]

So I decide to re-create those "app trigger flows".

In the solution, I opened the App for edit. Then Add a flow to one of button. Edit the flow and save. It looks alright but I cannot find the new flow in solution. How can I edit the flow?

[Pstork1 · Accepted solution]

If you create the app and flows in the solution from the beginning you will see the flows in the solution and can edit them there. Flows created inside solutions don't show up in My Flows, they are only available through the solution.

[Colchester]

In the solution, I edit the App and added 5 app-trigger-workflows. After 24 hours 3 flows listed in the solution. The other 2 flows still not show up although they are working. 

Is it normal or I need to do something to make them listed in solution package?

[Pstork1]

It will work that way.  The issue is that flows which aren't in the solution will cause problems if you export the solution and import it somewhere else.