Deal with System Owned flows

[PiZe0]

Does this bug already exist in our backlog?

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

Describe the issue

I have encountered a bug withing the "SYNC HELPER - Cloud Flows" Flow. I have a couple of flows "Load training data flow" or "Skill finder model status update flow" where "SYSTEM" is the owner of the flow. However, the sync helper always tries to get the actual owner of the record because there is no flow owner. Unfortunately it throws an error.

Expected Behavior

No response

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.37

What app or flow are you having the issue with?

SYNC HELPER - Cloud Flows

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

No response

Anything else?

No response

[Jenefer-Monroe]

Please go to the Admin Command Center > CoE Flows > Inventory. Validate that all flows are turned on and that there are no unmanaged layers as shown here.

Then run the following flow: CLEANUP - Admin | Sync Template v4 (Check Deleted)

Then wait to see if you still see this failure on the next inventory run.

[PiZe0]

Hello Jenefer,

i do have this issue a couple of weeks now. There are no unmanaged layers. I've done exactly what you suggest this week.

[Jenefer-Monroe]

I see. So the product is not storing these system owned flows in a way that notes who is the owner? What do you see when you browse here?

I'm not sure how to create a flow owned by system. Would it be possible to share the solution with me so that I can test? I can give you my email.

[PiZe0]

This flow was created by using the "Process Mining" Feature in Power Platform.

[Jenefer-Monroe]

Hmm I am not seeing this when I use that feature. I'll need to find a way to test this before I can address

[PiZe0]

This is the solution where the flow is stored. I can neither delete the flow nor the solution.

[Jenefer-Monroe]

Thanks for showing me that. I dont have Dynamics unfortunately so will need to find some other way to get a system owned flow.

[PiZe0]

I do have now multiple flows which end up in an error in the CoE StarterKit. They do not have an "owner" additionally they all are Dynamics Flows. For Example the "Sales Insights sequence daily usage flow". The interesting thing is, multiple dynamics flows are in this environment, and do not lead into an error in CoE, only 1 or 2 flows end up in errors. These 2 flows are the only ones which are "Enabled" and not "Disabled". But disabling them, does not help :(

[Jenefer-Monroe]

thanks for the additional info

[Jenefer-Monroe]

Can I please ask, what is returned from these two steps?

[PiZe0]

Sure .. here it is (sorry for german layout)

[Jenefer-Monroe]

Resolution here is as shown. We have another work item (#9164) for more thorough integration with System owned flows for V2

1. length(outputs('Get_actual_object_for_owner')?['body/value'])
2. @{''}

[Jenefer-Monroe]

Fix is available in Nov release. Please see latest release to see all changes or just download directly via https://aka.ms/coestarterkitdownload