'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Stop Power Automate from Sending Error Notifications to a Former Co-Owner
Question details
A former co-owner of a Power Automate flow continues to receive failure and error notifications despite being removed from the ownership list.
- Product
- Microsoft Power Automate
- Device & OS
- not provided
- Scenario
- Managing flow ownership and troubleshooting legacy error notification routing after team changes.
- Observed behavior
- Error notifications continue to be sent to a user who is no longer listed as a co-owner of the workflow.
Ensure you have Environment Maker or Administrator permissions to view and modify all flow connections, owners, and run-only user settings.
Update Flow Connections and Legacy Ownership Settings
Remove residual data such as legacy connections, connection references, and run-only configurations that still tie the flow to the former user.
Power Automate error notifications are not solely based on the current flow co-owner list. They can also be triggered by legacy ownership data, shared connections, run-only user settings, or environment notification subscriptions that remain active even after a user is officially removed from the owners list.
Open the flow in Power Automate and check the 'Connections' and 'Connection references' sections to ensure none are registered to the former user.
If a former user's connection is still active, edit the flow to replace or remove it. Authenticate with a current user's credentials or a dedicated service account, then save the flow.
Navigate to the flow's details page, review the 'Run-only users' list, and remove the former user if they are still listed there.
Trigger a test run of the flow to ensure it operates correctly with the new connections and ownership settings.
If the former user still receives alerts after updating the flow, contact your administrator to review tenant-level notification or governance settings.
Discover WPS Office for Your Daily Productivity Needs
While Power Automate handles complex workflow automation, your daily document, spreadsheet, and presentation tasks can be streamlined with WPS Office. It is a lightweight, free alternative to Microsoft Office that offers a familiar, easy-to-use interface and seamless transition for your team.
- 1. Visit the official website: Go to the official WPS Office website to download the latest version.
- 2. Install the application: Run the installer and follow the on-screen instructions to set up the software.
- 3. Start creating: Open WPS Office and instantly begin editing your existing Microsoft Office files without formatting loss.
Frequently Asked Questions
Why does a former co-owner still receive flow failure emails?
This usually happens because the flow is still using a connection, connection reference, or run-only user setting originally created by or assigned to the former owner, even if they were removed from the main co-owner list.
How do I remove a connection belonging to a former employee?
Open the specific flow in edit mode, locate the action steps using the old connection, and swap it out for a new connection owned by a current user or a generic service account. Save the flow to apply the changes.
Can environment settings override flow-level notifications?
Yes, sometimes governance policies or environment-level notification subscriptions might route failure alerts based on legacy data, requiring a Power Platform administrator to locate and clear them.
