While working with Power Apps and Power Automate for the IT Help Desk, I encountered the following error after adding a flow to the Power Apps app and later modifying it to add new SharePoint actions.
GetTickets.Run failed:
InvokerConnectionOverrideFailed
Could not find any valid connection for connection reference name 'shared_sharepointonline-2'

This usually happens when the Power Automate flow connection reference is not properly synced with the Power Apps app. For example, you added the flow to Power Apps first, then later added more SharePoint actions or changed the SharePoint connection inside the flow.
In my case, the app was calling the flow, but Power Apps could not find the correct SharePoint connection reference required by the flow.
Why Does This Error Happen
This error can happen because:
The flow was already added to Power Apps, but later you added a new SharePoint action to it.
The SharePoint connection used in the flow changed. The flow connection reference became invalid.
Power Apps is still using the old flow connection metadata. The flow was imported/copied from another environment or solution.
The user running the app does not have access to the connection used by the flow.
Fix: InvokerConnectionOverrideFailed in Power Apps
Follow the steps below to solve this error:
- Open your Power Apps canvas app. Go to Power Automate from the left side.
- Remove the flow from the app.

- Save the app. Then close and reopen it in Power Apps Studio.
- Add the flow again. Save and publish the app.
Now run the app again and test the button or screen where you are calling the flow.

Example:
Set(
varResult,
GetTickets.Run()
)
After re-adding the flow, Power Apps refreshes the connection reference, and the error should be fixed.
Conclusion
This is how you can fix the InvokerConnectionOverrideFailed error in Power Apps.
In most cases, this issue occurs when a Power Automate flow is modified after it has already been added to a Power Apps canvas app. Power Apps may still use the old connection reference, especially when new SharePoint actions are added to the flow.
To fix the issue, remove the flow from Power Apps and add it again. This refreshes the flow connection metadata, allowing Power Apps to call the flow successfully.
As a best practice, whenever you add new connector actions to a flow that is already connected to Power Apps, save the flow, remove it from Power Apps, add it again, and then publish the app.
Also, you may like:
- Power Apps Dropdown Show Only Unique Values
- Show a Different Home Screen Per User in Power Apps
- Power Apps JSON Polymorphic Error on _ownerid_value

Hey! I’m Bijay Kumar, founder of SPGuides.com and a Microsoft Business Applications MVP (Power Automate, Power Apps). I launched this site in 2020 because I truly enjoy working with SharePoint, Power Platform, and SharePoint Framework (SPFx), and wanted to share that passion through step-by-step tutorials, guides, and training videos. My mission is to help you learn these technologies so you can utilize SharePoint, enhance productivity, and potentially build business solutions along the way.