If you are a Dynamics CE Consultant, you should have heard of orphan records. Do you know Orphan flows do exist in Power Automate in a similar way….
A flow is considered to be an Orphaned flow when it don’t have a valid owner anymore. This can possibly happen when the creator or owner of the flow has left the organization and there is no co-owner or the owner for the flow. If the flow uses connections that require authentication, then it may start failing because the user identity is not valid anymore.
Admins can maintain continuity on the business process automated by the flow by adding one or more co-owners to it. Co-owners basically have full control over the flow just like the original owner, and can fix authentication for connections if any and enable the flow if it has been disabled.
Please note that only privileged users can view flows that do not have any valid owners. On the environment page from Flow Admin Center (https://admin.flow.microsoft.com/environments), go to “Resources” tab and then open the “Flow” list. Orphaned flows display “None” as their owner. Click “Load more” to load the next set of flows so as to ensure you have looked through all flows that might be orphaned.
How will you solve this problem?
- Manually you can add the flow a owner which will resolve the issue when the number of flows are in reasonably small in number. But if the number of Orphaned flows are in large number, you should look for next approach presented.
- Code way…using Power Automate cmdlets: Make sure you follow the instructions for setting this up.
Reference: How to manage orphan flows when the owner leaves the organization