Failed to parse invoker connections from trigger 'manual' outputs

[reveur007]

Hi all,

Good day! I am new to Power Automate and Power Apps. I just started working on a Power Apps app that triggers a Power Automate Flow to update some info on a SharePoint List. As the previous developer left and I got onboarded to work on this App- I changed to my work email account to get the access and work on the "Dev environment" with the connector to the SP list. But still I am getting this error inside the Flow at the very first step 

"Failed to parse invoker connections from trigger 'manual' outputs. Exception: Could not find any valid connection for connection reference name 'shared_sharepointonline_2' in APIM tokens header.

-Could anyone suggest anything on this, would appreciate it a lot. Best, reveur007

[reveur007 · Accepted solution]

Hi all, I got the error resolved! Within Power Apps, I removed the Flow [copy-pasted all the code in a notepad, not only call to the Flow] and added the Flow again [paste the code set]. The error is gone now! I think every time a new Dev starts working on this App-> this issue happens as the Flow specs need to be changed [Flow site] to map with the new Dev's account and Calendar: this messes up the Flow set up within Power Apps and causes the issue. Just FYI. Cheers!:)

[365-Assist]

In addition to @reveur007 reply.

There is a new way to call flows (Power Automate Pane) in PowerApps. When typing name of flow to connect flow to button ensure you choose the option ending in .Run Do NOT use the other option and type in Run. It will not fix the problem.

[misc]

Just wanted to thank you for this solution and as an FYI for anyone else, this issue also seems to occur if microsoft decides you need to re-authenticate your connection to every one of your flows, it's not just when a new 'owner' is added to the app/flow.

[edobaria]

Yes, I am facing the same issue :(, any solution?

[kiki_515]

I encountered same error and it's intermitter, and some users hv this issue some users don't.

[Anupama_live]

Another alternate solution is to refresh the flow in the PowerApp instead of removing and readding the flow with code. It fixed for me the same issue by refreshing the flow.

[limaluca]

Hello. On your flow settings, check your connections "run-only" on the lower left menu. 

All the connections must be used by the same user.

[happyskier22]

I had this issue as well. What helped was to edit my flow in power apps and reselect my connection on the action box. This made it work for me.