Power Platform Community Forum Thread Details

Hi, I’m trying to invoke Copilot Studio directly through an agent flow.
When I call a single agent, the request works successfully. However, when I try to invoke an agent that has child agents, the request fails and returns an error.

Could you please help me understand the possible reasons for this behavior?
Any insight into why agents with child agents cannot be invoked successfully would be very helpful.

Categories:

Calling actions from Copilot Studio

Hey @AT-06030333-0

A few likely causes come to mind.
If the agent works when called directly, but fails when that agent includes child agents, the first things I would check are:

Authentication or identity mismatch between parent and child agents. Microsoft lists errors such as ConnectedAgentAuthMismatch when the orchestrating agent and sub-agent don’t line up on auth/configuration.
Child agent reference/configuration issues. Microsoft also documents ConnectedAgentBotNotFound, which points to cases where a sub-agent in a multi-agent setup can’t be found or resolved properly.
Agent flow input/schema drift. If inputs on the flow changed after it was added, Copilot Studio can fail until the flow/tool is removed and added again. Microsoft documents this as BindingKeyNotFoundError.
Multi-agent behavior not matching test vs published runtime. There are known cases where child-agent behavior works differently in Studio/testing versus deployed/runtime scenarios, so it is worth checking whether the failure only happens from the agent flow entry point or only after publishing.

A few practical checks:

Confirm the parent and child agents are in the same environment/solution path and still published.
Reopen the agent flow action and remove/re-add the agent or flow step if any inputs were changed later.
Check the exact error text/code for anything like ConnectedAgentAuthMismatch or ConnectedAgentBotNotFound.
Test whether the issue happens only when the parent is invoked through the agent flow, versus directly in Copilot Studio.

If you can share the exact error message/code, it will be much easier to narrow down whether this is auth, environment/reference, or flow schema related.