It sounds like you're dealing with a common issue in Power Automate when a former employee's connections are still being referenced. Here are some steps you can take to fix this:
1. Remove the Former Employee's Connections: Ensure that all connections created by the former employee are completely removed from the flow. You can do this by going to the flow's settings and checking the Connections section.
2. Reauthorize Connections: After removing the old connections, reauthorize the necessary connections with the current user's credentials. This will ensure that the flow uses valid and current connections.
3. Check for Hidden References: Sometimes, flows might have hidden references to old connections. Review the flow thoroughly to ensure there are no hidden references to the former employee's connections.
4. Update Flow Owner: Make sure the flow owner is updated to the current user or team responsible for maintaining the flow.
5. Test the Flow: After making the changes, test the flow to ensure that it runs without any errors and that the email delivery action works correctly.
Here is a link to Microsoft Learn that can assist with Orphaned flows: Manage orphan flow when owner leaves org - Power Automate | Microsoft Learn It uses PowerShell to make adjustments to flows.
This community is supported by individuals freely devoting their time to answer questions and provide support. They do it to let you know you are not alone. This is a community.
If someone has been able to answer your questions or solve your problem, please click Does this answer your question. This will help others who have the same question find a solution quickly via the forum search.
If someone was able to provide you with more information that moved you closer to a solution, throw them a Like. It might make their day. 😊
Thanks
-Mark
Share
Report
スクリーンショット 2024-12...
All responses (
Answers (
1,351
