Re: PowerApps error when workflow is run "InvokerConnectionOverrideFailed" on Sharepoint
We've been struggling with the same error for quite some time, but we're glad to have finally found its root cause.
The error follows a distinct pattern: it emerges when using a single automated flow across two different applications, particularly when configuring the same flow in multiple apps with different underlying connections.
By 'different underlying connections,' I mean users utilizing various Microsoft accounts.
For instance, in App_1, the flow is configured using abc@xyz.com,
while in App_2, it's configured using qwe@xyz.com.
This discrepancy causes ambiguity, leading the flow to struggle when making API calls.
The question then arises: Can we use a single automated flow in different PowerApps?
Yes, it's possible.
Solution-:
The solution involves ensuring that a flow 'FLOW' integrated/used in multiple PowerApps like 'App_1' and 'App_2,' is connected to underlying connections (such as SQL or SharePoint) using the same Microsoft account. This consistency in underlying connections (SQL or SharePoint) is crucial to prevent these errors.
Hope this helps in resolving the issue. Happy learning!
