[CoE Starter Kit - BUG] Manage Permissions App fails when trying to delete orphaned flows

[Knowone27]

Does this bug already exist in our backlog?

• I have checked and confirm this is a new bug.

Describe the issue

When trying to delete any number of orphaned flows in the Manage Permissions app I get the following error.
"Deleting some flows failed, try to delete via product UX"

Expected Behavior

Whether it be 1 or 100 flows, I expect the app to be able to delete the number of flows selected, but it fails no matter how many flows are selected.

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.32.2

What app or flow are you having the issue with?

Manage Permissions

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

1. Login to Power Apps as the Power Platform Global Administrator
2. Navigate to the Manage Permissions app
3. Click on the "Flows" tab
4. Click on the "Orphaned Flows" Button
5. Click the checkbox of any, or all flows from the list
6. Click the "Delete Selected" button
7. Wait a minute for the error message to popup saying "Deleting some flows failed, try to delete via product UX"

Anything else?

I have reached out to our MS contact and he advised me to submit an issue here. He was able to see the issue in a call we had to discuss a potential support ticket.

[Jenefer-Monroe]

Can you please browse to one of the flows and try to delete manually? This way we can see the error message you get.

[Jenefer-Monroe]

And also, are you logged in as a user with the Power Platform Admin role?

[Knowone27]

Can you please browse to one of the flows and try to delete manually? This way we can see the error message you get.

Deleting manually works correctly, it does not have any errors. Only the "Manage Permissions" application. There are hundreds of flows to delete, and deleting each one on an individual basis would take days or weeks.

And also, are you logged in as a user with the Power Platform Admin role?

Yes, as described in the steps to reproduce using the Power Platform Global Administrator role.

[Jenefer-Monroe]

Can you validate, are these solution aware flows?

We did just, in the July release, unblock deleting of solution aware flows through the helpers:
#3052

[Knowone27]

These are older flows from 2021-2022, so I do not believe any of them are in solutions.

[Jenefer-Monroe]

ok you'll need to open the flow that is called and see where it is failing then.
Browse to this flow, open the recent run and show me what happens inside there
HELPER - CloudFlowOperations

Here, for example, you can see it failing due to a product limitation.

[Knowone27]

ok you'll need to open the flow that is called and see where it is failing then. Browse to this flow, open the recent run and show me what happens inside there HELPER - CloudFlowOperations

Here, for example, you can see it failing due to a product limitation.

it does not appear to be failing

[Knowone27]

Just confirmed, it does not show any failures in the 30 day run history

[Jenefer-Monroe]

yes we catch these failures. Please open the run for when it fails for you and see what happens there.

[Knowone27]

Okay, this is what it's giving me

[Jenefer-Monroe]

Did you erase the inputs? Or were they blank?

[Jenefer-Monroe]

Can you please share the body of the output?

[Knowone27]

Okay, sorry it hadn't populated yet. one min.

[Knowone27]

{
"error": {
"code": "EnvironmentAccessDenied",
"message": "You are not permitted to make flows in this '9407f998-df4c-49e1-bb48-b181e9e3f8dc'. Please switch to the default environment, or to one of your own environment(s), where you have maker permissions."
}
}

this is the body of the output

[Jenefer-Monroe]

The user that is logged in to the app appears to not have elevated permissions for that environment.

Can you please validate that the user logged into the app has the power platform admin role assigned?
Microsoft Azure Users > Your User > Assigned Roles
Ensure Power Platform Administrator is Direct and Permanent

[Knowone27]

Confirmed the account roles are permanent

[Jenefer-Monroe]

Is that envt your default environment?

[Knowone27]

Is that envt your default environment?

You mean in Azure? I think we only have one Azure Environment.

[Jenefer-Monroe]

no I mean the envt in which the flow lives. Is the flow you are trying to delete in your power platform default environment?

[Jenefer-Monroe]

I will presume that they are, but please do confirm.

It looks like the dev that made this app sent in the id of the envt and not the name.
Many calls take "name" not "id" and this is only obvious if one tests default as its the only one where they arent identical.

Basically for a default envt
if id = abc123a1-aabb-bbaa-aa11-a11aa11a1a1a
then name = Default-abc123a1-aabb-bbaa-aa11-a11aa11a1a1a

[Jenefer-Monroe]

quick testing shows the issue is only with delete, not updating permissions or browsing to the app, etc

fixes are to the custom pages as shown:

[Jenefer-Monroe]

Thanks for posting, unless I hear from you otherwise I'll assume these were flows in default.
And that we are now local fixed for August release.

[Knowone27]

Yes Jenefer, These flows are in default. So in the upcoming release (August) these fixes will be rolled out?

[Jenefer-Monroe]

Thats correct, thanks for confirming!

[Knowone27]

Thats correct, thanks for confirming!

Thanks, Jenefer. You've been a major help! I'll go ahead and close this thread.

[Jenefer-Monroe]

An early release of the August bits are available for testing.
Please see our Preview Builds

Please test for us! But do not install these in your production environment but rather in a test envt to get us feedback.

Here are the August release candidate solutions.
Core 4.33.14
Gov 3.24.1
Nurture 3.18.1

And the PBIT files
Production CoE Dashboard August 2024
Governance Dashboard August 2024

It contains all the changes targeting August: https://github.com/orgs/microsoft/projects/195/views/59

Including these two very impactful changes:
#8016 - Update Kit to respond to new Power Platform Admin Role PIM feature
#8482 - Integrate new audit log methodology into the kit for API reduction. Please see issue for setup instructions.

[Jenefer-Monroe]

fixed in August release https://github.com/microsoft/coe-starter-kit/releases/tag/CoEStarterKit-August2024