search

microsoft / coe-starter-kit

Other
748 stars 221 forks source link

[CoE Starter Kit - BUG] Orphan Flow/Permission App not inSync #8719

Closed Sinder088 closed 2 months ago

Sinder088 commented 2 months ago

Does this bug already exist in our backlog?

Describe the issue

We have been running the Orphan flows for just over a month now. Every Friday we receive a number of emails where managers have not responded. 2 weeks ago i used the Manage Permission app to reassign or delete these apps/flow. Both last week and this week i received Orphan emails showing the same apps/flows which i have already resolved. When i try locate them in the manage permission app, they are no longer showing orphaned.

Any idea why this would happen? It almost seems like the Orphan flows are not retrieving the latest data.

image image

Expected Behavior

Orphan Flows should retrive the most updated data and not show apps/flows that are not in fact orphaned.

What solution are you experiencing the issue with?

Governance

What solution version are you using?

3.21

What app or flow are you having the issue with?

Request Orphaned Objects Reassigned (Parent)

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

No response

Anything else?

No response

AB#3913

Jenefer-Monroe commented 2 months ago

We had an issue recently that was fixed in the May version of the kit, which it appears you are on. https://github.com/microsoft/coe-starter-kit/issues/8060

  1. See change Can you please open this flow in edit mode? Request Orphaned Objects Reassigned (Child) Do you see this at the top? image

  2. See runs Can you please go to that same flow's all runs : Request Orphaned Objects Reassigned (Child) Filter to Running, what is the oldest run (start time X days ago) image

Sinder088 commented 2 months ago

Hi

  1. Yes i do see it:

  2. Seems oldest running is 2 days ago.

    image
Jenefer-Monroe commented 2 months ago

Do you have this flow running and passing? It should run weekly. CLEANUP - Admin | Sync Template v3 (Orphaned Makers)

Sinder088 commented 2 months ago

Yes, it ran successfully yesterday: image

Sinder088 commented 2 months ago

When looking into the flow i see the condition is showing false, hence the "mark as not orphaned" is not running. image

Jenefer-Monroe commented 2 months ago

Interesting, I'm not sure how you ended up with nulls in your derived owner field. Nulls there will appear as orphan to other processes.

How many of these objects are you seeing? Are we talking about tens of these?

Sinder088 commented 2 months ago

Are you asking how many objects (App, flows, bots) i am seeing with null owner?

Jenefer-Monroe commented 2 months ago

From this original query, you say you are seeing a repeat ask about a number of objects you tried, to clean. How many is that?

Sinder088 commented 2 months ago

There are about 124 in total that keep re-occuring.

image

Jenefer-Monroe commented 2 months ago

ok. if you go into the PPAdmin app, and filter to where derived owner contains no data, how many result there? image

Sinder088 commented 2 months ago

48 Flows

Jenefer-Monroe commented 2 months ago

and how many of those 48 are not marked orphan?

Sinder088 commented 2 months ago

All are marked orphaned.

Jenefer-Monroe commented 2 months ago

Are any of these the ones showing up for you in the recurring list? image

Sinder088 commented 2 months ago

Only the ones showing Unknown from the image above.

Jenefer-Monroe commented 2 months ago

We do mark the flow as orphaned when you set the ownership through the app so I"m not sure whats happening for your case. image

Jenefer-Monroe commented 2 months ago

Can you please run this flow and see if it resolves? CLEANUP - Admin | Sync Template v4 (Check Deleted)

Sinder088 commented 2 months ago

I have been using the Manage Permission app to reassign ownership. Is that the correct approach?

Sinder088 commented 2 months ago

CLEANUP - Admin | Sync Template v4 (Check Deleted) This last ran successfully 5 days ago. I have kicked it off again now.

The orphan flow just run again a few hours ago and still seeing most of the flows showing up again. So strange. I checked one of them and it is showing on the orphan list in the manage permissions app but when i open the flow i see that i am the primary owner (hence it is not orphaned).

Jenefer-Monroe commented 2 months ago

Manage Permission app is fine. I think we'll have to take a single instance to debug.

Is this the mail you are getting the list in? image

  1. Find one of the flows you do not expect to see getting to you from the orphan flow because you re-assigned it, and find it in the Power Platform Admin View

    • Is it shown as deleted?
    • Is it shown as orphan?
    • Is the correct person shown as derived owner?

  2. Find one of the flows you do not expect to see getting to you from the orphan flow because you deleted it, and find it in the Power Platform Admin View

    • Is it shown as deleted?
Jenefer-Monroe commented 2 months ago

closing out as no further action for starter kit team

Sinder88 commented 2 months ago

So the flow ran again this morning and many of the previously orphaned flows are still coming through. see below images: here is the email i receive: image

Here is what admin app is saying: image

I don't understand why its still sending emails on this one.