Unanswered

Failed PA Export

(0) Share

Report

Posted on by cycle4passion

I have create my PA with no errors of significance beyond delegation warnings. It was my first PA, so admittedly it was a long time in production. When trying to export I was getting a error to the effect "Flow not Found". I needed a smaller subset of this app anyways, so copied it via save As, simplified it significantly, and removed unnecessary connections. Checked it again without errors. It functions as expected. On trying export I get the error below.

I am only using only 1 flow in this subset project, I removed the connection, and added it back but get the same error. I looked through every control and could not find any other flow references.

The flow reference look like this:

Launch(BedlisttoSharepointforPrinting.Run(BedlistHTML.HtmlText).link);

Categories:

Building Power Apps

I have the same question (0)

All responses (5)

Answers (0)

WarrenBelz 153,113 Most Valuable Professional on at

Like (0)

Report

Hi @cycle4passion ,
Try deleting the Flow from your data sources and then re-attaching it.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Was this reply helpful? Yes No
cycle4passion 94 on at

Like (0)

Report

@WarrenBelz thank you for your direction.

I had tried this before, but to be sure.

I removed the flow connection (only one in project)
I deleted the 2 code references to this flow.
I saved the project, closed it, and reloaded.
I added the flow connection again via action x 2
Same error as screen shot above..

I saved a copy of this small subset app
I deleted everything I could, leaving 1 screen, 1 button, no other flows, connections, data, or customized settings for the App, Screen or button except Button.OnSelect simply does Set(link, BedlisttoSharepointforPrinting.Run("Hello").link);
Same Error as above

I created a fresh new app, added a button, added the action: Button.OnSelect simply does Set(link, BedlisttoSharepointforPrinting.Run("Hello").link);

This runs correctly without errors. Saved it, Exited, and export works fine.

Seems like I have accumulated some bad flow reference that doesn't appear to be user facing. This smaller subset app is easily recreated from scratch, but the bigger issues is the much larger parent app, from which this subset was copied, is having the same error and I am not excited about recreating that.

Was this reply helpful? Yes No
WarrenBelz 153,113 Most Valuable Professional on at

Like (1)

Report

Thanks @cycle4passion ,
What you are experiencing obviously should not be happening and I was just trying some work-arounds.
Other than exporting an re-importing it after you have deleted the Flow, the only other thing I can suggest
is lodging a Support Ticket with Microsoft

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Was this reply helpful? Yes No
cycle4passion 94 on at

Like (0)

Report

@WarrenBelz still waiting on support ticket help. I can confirm that I have some old reference to 2 flows that do not exist anymore which is causing the problem. I cannot find code references, so I think it is some non-user facing problem.

Currently referenced/available flows with IDs
Bedlist to Sharepoint for Printing - 869ae057-9ab6-4957-967c-08b5b4732a7d
Immediate or Delayed Message - 1aa883a8-03ea-447d-9cce-8fd4dfafcad5
PA Delete Patient Image File When Patient Deleted - 1d217f4e-748f-4ca0-87bb-43f5d5383d83
PA Photo Upload to Sharepoint with Return Link - e7d797e0-fc71-42c1-82eb-7481fe0a41a7

On Export Error:
Could not find flow 'b51b252b-2d04-43be-bf49-f6bb287d3d29'.The provided flow '44a456a5-a6ca-43eb-9d7a-3f7e0c0bd321' has been deleted.

Census VU Says it is using 6 (see image), “The PA Send Immediate or Deleted Teams Message to Person” and
“PA Delete Photo if Exists On Patient Delete” are old ones. I still cannot find their reference in code.

flows.jpg

Was this reply helpful? Yes No
WarrenBelz 153,113 Most Valuable Professional on at

Like (0)

Report

@cycle4passion ,

I am sorry to hear that.

As I mentioned, this should not be happening and I have seen a few other posts where "ghost" connectors will not disengage. This is clearly a bug that Microsoft needs to address.

Was this reply helpful? Yes No