Flow is not displayed in my powerApp

(3) Share

Report

Posted on by UrlbergerP

Hello i am currently working on a PowerApp that is using a couple of PowerApps triggered Flows.

Unfortunately a certain Flow is not displayed in the PowerApp, so i cant add him to my app.

The flow did already exist in the App and was connected to it but i changed it and needed to update it.

So i deleted it and then wanted to re-add it which is now not possible anymore. The problem is existing with all my flows i think, because no other flow is displayed (even if already connected and working). If I add a new flow, i can use it, but the is is then not displayed in my flow overview anymore.

Does anyone have the same problems?

It's the same environment so there is not the problem.

Categories:

Building Power Apps

I have the same question (0)

All responses (27)

Answers (2)

CU26081512-0 2 on at

Like (1)

Report
Copy link

Link copied!

I had this issue and had to add the flows to my Powerautomate solution before they would show up in Powerapps. Once added to solution, refresh the available instant flows in Powerapps and they appeared as expected.

Was this reply helpful? Yes No
RamiAH 3 on at

Like (1)

Report
Copy link

Link copied!

I can confirm JonathanGibbs fix worked for me.

Was this reply helpful? Yes No
JonathanGibbs 313 on at

Like (3)

Report
Copy link

Link copied!

This fix worked for me:
Edit the flow that is refusing to appear. Note the parameters in the initial trigger (Power Apps v2) action. Delete the action. Insert a new Power Apps V2 trigger action. Recreate the parameters you noted, and save the flow.
It then appears in Power Apps listings.
Arrived at this after much frustration messing around with solutions, resaving apps with different names, etc etc. No doubt those fixes work in some cases but this one worked when they all failed!

Was this reply helpful? Yes No
stingray 196 on at

Like (2)

Report
Copy link

Link copied!

This is the way.

Was this reply helpful? Yes No
ThePercio 23 on at

Like (2)

Report
Copy link

Link copied!

solid advice from singray. +1 to that.
This is the way.

Was this reply helpful? Yes No
stingray 196 on at

Like (2)

Report
Copy link

Link copied!

To be honest, especially if anyone is starting off with the Power Platform, first thing you should do it create a solution, then create your app and flows in there, and add connection references and environment variables for data sources, will be much better in the long run, especially if you plan to have ALM to the business.

But yeah, create a solution, put your app in, (hopefully you can find it when selecting add existing), then add the flow you want to add to the canvas app the same way to the solution, then look for the flow in the canvas app.

Was this reply helpful? Yes No
Engtech05 8 on at

Like (1)

Report
Copy link

Link copied!

So, wait are you telling me that I have to create a solution and add the app and the flow to it first in order to actually adding the flow to the app?

Was this reply helpful? Yes No
stingray 196 on at

Like (1)

Report
Copy link

Link copied!

I've not had this issues for a while, is your flow is in the same solution as your canvas app with all the connection references?

Was this reply helpful? Yes No
Engtech05 8 on at

Like (1)

Report
Copy link

Link copied!

Soooo...... When is MS going to get this fixed. I have flows that need to be associated with Power Apps, but no, it won't happen. Even though they said the fix was supposed to be out the week of March 3rd. See attached image from MS Power Platform. This is most aggravating, that this issue has been around for months and still no fix. How does MS expect companies to run who depend on programmers to get projects out when no foreseeable fix is coming?!

Was this reply helpful? Yes No
philifova 125 on at

Like (1)

Report
Copy link

Link copied!

Tried this but URL is not the same. Tried Renaming the buggy App with new one and Rename the new one with the same as old but they're still different URL

Was this reply helpful? Yes No