PowerApp error when flow triggered by button: InvokerConnectionOverrideFailed

PowerApp error:

TestFlow.Run failed: { “code”: “InvokerConnectionOverrideFailed”, “message”: “Failed to parse invoker connections from trigger ‘manual’ outputs. Exception: Could not find any valid connection for connection reference name ‘shared_sharepointonline’ in APIM tokens header.” }

Resolution:

When flow is added to PowerApp e.g. a button, the PowerApp stores a “definition” of the flow (i.e. what it needs to run – inputs, outputs, and connections that it will need to run the actions in it). When you change a flow, PowerApp needs to refresh its definition of the flow and normally re-adding it to the button is enough. But if you have added actions requiring a connection e.g. Create SharePoint List Item, then even though you may have other actions using the same sharepoint connection that worked before, you might get this error because the new action needs to be given a connection from power app at run time. Re-adding the flow to the button doesn’t trigger PowerApp to fully refresh its definition of the changed flow. It will know about inputs and outputs changing but not that it needs to supply a connection for another action. One way to trigger PowerApp to fully refresh the definition of the flow is to edit the new SharePoint action in flow and add a new connection to it. Then when you re-add it to the button in PowerApp it will fully refresh its definition of the flow and will recognise that it needs to supply the connection to more actions at run time.

Leave a comment