Open Alyson95170 opened 3 months ago
Hello. It looks like we resolved this in a later build. Please see https://github.com/microsoft/coe-starter-kit/issues/4511
Thanks Jenefer, I am using the latest version of the Governance components and still having this issue
Can you please check for unmanaged layer on the flow for me?
If none, can you please see what happens above in the flow run here?
How many records are returned for the two List operations? And which path does it go down?
Hi Jenefer I can confirm there is no unmanaged layer
The manager has 4 employees that have left the business, each employee has less than 30 apps and flows but altogether there are 38 orphaned objects
each one of the 4 goes the yes route.
ok thank you. Will target making this simpler for May release and try to send you an easy local fix as well.
That's great thanks Jenefer
Not a simple change after all. Moving out to June
Does this question already exist in our backlog?
What is your question?
Hi, we have recently turned on the Request Orphaned Object flows, I have noticed an error when a manager has multiple employees no longer with the business, and there are over 35 Orphaned objects![image](https://github.com/microsoft/coe-starter-kit/assets/82215551/d1b309a0-8b8b-464d-9bb6-a999875a35ec)
Is there any way this can be avoided or would these ones just be looked at individually?
What solution are you experiencing the issue with?
Governance
What solution version are you using?
3.16
What app or flow are you having the issue with?
Request Orphaned Objects Reassigned (Child)
What method are you using to get inventory and telemetry?
Cloud flows
AB#2705