Skip to main content

Notifications

Announcements

Replay: Power Platform Community AMA - Copilot Studio | April
Welcome to the Power Platform Communities
News and Announcements icon
Community site session details

Community site session details

Session Id : wNy0iOV3kTq/64RS88bsCW
Power Platform Community / Forums / Power Automate - Using Flows / Failed to parse invoke...
Power Automate - Using Flows
Answered

Failed to parse invoker connections from trigger 'manual' outputs

Like (1) ShareShare
ReportReport
Posted on 13 Apr 2022 16:52:01 by reveur007 124

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 

Apr132022FlowError.png

 

"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

 

  • happyskier22 Profile Picture
    happyskier22 2 on 10 Jul 2024 at 19:40:48
    Re: Failed to parse invoker connections from trigger 'manual' outputs

    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.

  • limaluca Profile Picture
    limaluca 17 on 22 Dec 2023 at 18:39:28
    Re: Failed to parse invoker connections from trigger 'manual' outputs

    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.

  • Anupama_live Profile Picture
    Anupama_live 70 on 13 Dec 2023 at 04:30:12
    Re: Failed to parse invoker connections from trigger 'manual' outputs

    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.

  • kiki_515 Profile Picture
    kiki_515 14 on 06 Dec 2023 at 10:20:22
    Re: Failed to parse invoker connections from trigger 'manual' outputs

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

  • Trinity365 Profile Picture
    Trinity365 38 on 17 Mar 2023 at 15:56:00
    Re: Failed to parse invoker connections from trigger 'manual' outputs

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

  • misc Profile Picture
    misc 588 on 02 Feb 2023 at 17:02:52
    Re: Failed to parse invoker connections from trigger 'manual' outputs

    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.

  • 365-Assist Profile Picture
    365-Assist 2,312 Super User 2025 Season 1 on 05 May 2022 at 05:02:02
    Re: Failed to parse invoker connections from trigger 'manual' outputs

    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.

     

    365Assist_0-1651726832064.png

     

  • Verified answer
    reveur007 Profile Picture
    reveur007 124 on 13 Apr 2022 at 23:19:58
    Re: Failed to parse invoker connections from trigger 'manual' outputs

    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!:)

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Replay: Power Platform Community AMA - Copilot Studio | April
Welcome to the Power Platform Communities

Quick Links

Understanding Microsoft Agents - Introductory Session

Confused about how agents work across the Microsoft ecosystem? Register today!

Markus Franz – Community Spotlight

We are honored to recognize Markus Franz as our April 2025 Community…

Kudos to the March Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
WarrenBelz Profile Picture

WarrenBelz 146,679 Most Valuable Professional

#2
RandyHayes Profile Picture

RandyHayes 76,287 Super User 2024 Season 1

#3
Pstork1 Profile Picture

Pstork1 66,015 Most Valuable Professional

Leaderboard

Featured topics

Restore a deleted flow

Product updates

Microsoft Power Platform Community release plans