List Flows as Admin returning FlowNotFound (Error 404) when using Get Flow as Admin from same data

(0) Share

Report

Posted on by m3ngi3

725

Wondering if anyone else has noticed this:

I installed the CoE Kit: more info here https://github.com/microsoft/powerapps-tools/tree/master/Administration/CoEStarterKit
In this Kit there is a Flow that uses the Power Automate Connector to get all flows of an environment. One of the actions is to List Flows as Admin

In the OUTPUTS there is a Flow found:
And then an Apply to each loop will Get Flow as Admin to get info on the flow that was listed in the previous step

The strange thing is that the List flow is outputting a Flow that cannot be found in the Get flow action 🤯

Is the List Flow action looking somewhere else than the Get Flow action??

Categories:

Using connectors

I have the same question (0)

All responses (6)

Answers (1)

edguerre Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

Hi Django,

Both actions look at flows on a selected environment that you have admin access to. It might be hitting some sort of permission issue, but that should not happen. I have not been able to reproduce this on my own tenant however.
For this scenario, I recommend opening a support ticket in order to engage with the connector team.

Was this reply helpful? Yes No
m3ngi3 725 on at

Like (1)

Report
Copy link

Link copied!

Thank you for the fast reply!
It cannot be a permission issue, as this account is Power Platform Admin (as well as Global Admin for now) so I thought maybe one of the connectors is looking at a different table (maybe a table including older deleted flows or something) but will definitely recommend to log a ticket for the environment this is happening 👍

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

Like (1)

Report
Copy link

Link copied!

My pleasure! Sorry for not providing a more in depth explanation but the fact is that the connector page does not reference where the information is fetched from: https://docs.microsoft.com/en-us/connectors/flowmanagement/. But it might indeed be looking at a somewhat different table, that would explain the behavior you faced.

Was this reply helpful? Yes No
Verified answer

m3ngi3 725 on at

Like (0)

Report
Copy link

Link copied!

An update from the Microsoft Engineers:
It looks like we ran into an issue, where the Flow is deleted , but the logic app which runs behind the Flow did not, which is why it is not there for ‘Get Flow’ but List Flow under admin pulls it. It’s a rare occurrence, however, we are working towards this issue and fix the actions.
Can` you confirm from the user whether they want this Flow or not. We can either perform cleanup and remove it, or restore it back for this user. Upon your response, we will proceed with the cleanup, and post that you won’t see this issue.
So I guess there could be a difference in where the two actions look. Microsoft will fix this for us in this specific tenant 👍

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @Django I am having the same issue with CoE. How can I remove the 'deleted' flow?

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Ignore my last message - I found that although I couldn't edit the deleted flow, it did allow me to click Delete!

Was this reply helpful? Yes No