@skolisetti
Hey Mate,
A flow turns into an orphaned flow when it does not have a valid owner anymore. This often happens when the creator or owner of the flow has left the organization and there is no co-owner. 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.
Reference article https://support.microsoft.com/en-in/help/4556130/manage-flow-when-owner-leaves-organization
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!
