Answered

Could not find flow error

(0) Share

Report

Posted on by KenAllgood1

I'm getting this error when trying to do an export package on my Powerapp so I can pull it into a Dev environment. I've seen others get this error and the reply was get it the GUID from the URL while editing the flow. However, from what I am seeing, the GUID for the flow isn't showing there (presumably a change in the Powerapps environment). Anyone know how to find the guid of the relevant flow? My powerapp uses 6 flows in different screens, so it will be a pain to have to remove each one from code, remove it from the app, re-add to the app, and re-add to the code.

Categories:

Building Power Apps

I have the same question (0)

All responses (7)

Answers (1)

Sort by

Pstork1 69,481 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Did you build your Power App and related flows in a solution? If you did then did you use Connection References for the connections in the flows? Those two steps are required if you want to easily move an app and related flows from one environment to another.

Was this reply helpful? Yes No
KenAllgood1 27 on at

Like (0)

Report
Copy link

Link copied!

For now, we actually want to just pull it back into the same environment (I know I said a different environment, and we will later on). So I really just want a DEV copy of the powerapp (using same dataflows is fine). I actually did this previously and have 2 versions of the app, but I need to recopy the LIVE version to our dev one (probably making a 3rd copy for now).

Was not in a solution. I added the Powerapp to a solution (couldn't add Dataflows, wouldn't list them??). Managed to export, but not able to import because of managed vs unmanaged, trying to work through that right now...

Was this reply helpful? Yes No
Pstork1 69,481 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

The way that Power Apps connects to flow changed about a month ago when they added the Power Automate panel icon to the left sidebar. I'm not sure you'll be able to import a second DEV copy of the power App without dropping and re-adding all the flows unless its in a solution.

The problem is that manually triggered flows can't be imported into a solution after they are built. They need to be created inside the solution. I have been able to import them if I change the trigger temporarily, but that would require re-adding them to the Power App after it is added to the solution.

Sorry, but without building it in a solution to begin with I don't know of an easy way to do this. Since you just want another copy in the same environment did you try doing a Save As?

Was this reply helpful? Yes No
KenAllgood1 27 on at

Like (0)

Report
Copy link

Link copied!

Well that's not good

I was able to do the save as into a new powerapp, but that has the same export error on flow ID. What we're trying to do is have a dev and live copy in same environment. To push changes from dev to live in past, we were able to export package for DEV and import to the live. May have to work on the Solution side to do that then. Our Flows are all calls to SQL stored procs, so not THAT much to do, just couple of params to add for each. FYI, technically the live version is not "LIVE" yet, but it's in testing. We've moving onto phase 2 of development, and don't want to touch the version they're testing. Don't anticipate the stored procs changing anytime soon.

Was this reply helpful? Yes No
Verified answer

Pstork1 69,481 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

I would suggest doing the refactoring required now to get it built in a solution. That may require rebuilding each of the flows from scratch from inside the solution. But that should make the total package much more stable and transportable. I would also suggest using an actual Developer environment for the Dev work to keep it separate from the other version. Once you have it all in a solution you'll be able to Export/Import the solution between environments as an unmanaged solution. One additional point. Make sure you create actual Connection References in the solution too and use them in the flows.

Was this reply helpful? Yes No
LakshmiT Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

I am also getting the below error message and flow is not showing as it is deleted. How to restore that, can any one help?

Error: Could not find flow '221*****8172-*4c6-8**0-a3b***87f'.

Was this reply helpful? Yes No
Pstork1 69,481 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Please post this as a new question. You'll get more responses and others will be able to find the answer more easily later.

Was this reply helpful? Yes No