error while using office 365 connectors inside child flows

[elizi]

I'm trying to use office 365 connectors such as "Send an email (v2)" inside a flow that been called as a child flow from other flow as a part of the solution object and been getting the attached error, what can been done? is anyone encountered this issue and managed to overcome it?

the error message:

{

"code": "InvokerConnectionOverrideFailed",

"message": "Failed to parse invoker connections from trigger 'manual' outputs. Exception: Could not find property 'headers.X-MS-APIM-Tokens' in the trigger outputs. Workflow has connection references '[\"shared_office365\"]' with invoker runtime source."

}

the flow:

[ChristianAbata]

hi @elizi  please see if thsi solution could help you.

https://powerusers.microsoft.com/t5/Building-Flows/Flow-does-not-work-inside-SharePoint-Online/m-p/4...

[mdimillo]

Did you ever resolve this?  I am having the exact same issue, and am stumped.  The linked solution does not apply to me (I don't think) since I am not triggering the flow from a button in a SP list.  I am trying to create a net new item in a SP list.  My child flow is triggered "manually" from an initial flow.

[ldelgado1129]

I am having the same issue in Power Automate using a Parent and a child Flow:

The Parent Flow is failing: 

Here is the error message:

Failed to parse invoker connections from trigger 'manual' outputs. Exception: Could not find property 'headers.X-MS-APIM-Tokens' in the trigger outputs. Workflow has connection references '["shared_office365users"]' with invoker runtime source.

In the child flow, I soon as add the 'Get user profile (V2) '    from Office 365 Users action to my child flow, I get the error in the parent flow. The child flow never runs.

Has anyone found a solution to this?

I am trying to use the 

[Anonymous]

I had the same problem and found this video by Alireza Aliabadi. It involves PowerApps, but I found out that the same worked for flow. You have to build your childflow first, and then add the "Run a child flow" action AFTER your child flow is finished. Watch it here: https://youtu.be/OpE4U96-ys8

[Schumanar]

I know this is an old chain, but I wanted to post a possible solution for anyone who stumbles upon it now. I received this same error when I added a new connector to my child flow and forgot to update that connector to not use 'provided by Run-Only User' connections.

Hope this saves someone some trouble!