Power Platform Community Forum Thread Details

I'm building a multi-market chatbot in Copilot Studio. At the start of the conversation, the user selects their market (Europe or Asia). Based on this selection, I want a specific child agent to take over and answer the user's questions using its own knowledge source.

Expected flow:
1. User selects "Europe" → Europe child agent handles all subsequent questions using Europe-specific knowledge
2. User selects "Asia" → Asia child agent handles all subsequent questions using Asia-specific knowledge

Each child agent has its own SharePoint knowledge file and no custom topics — it should rely on Generative AI to answer.

What I have set up so far

In the main agent's Conversation Start topic:

User selects market → Set Global.Market

└─ Condition: Global.Market = "Europe"

└─ Agent node: Europe Affiliate (child agent)

└─ Condition: Global.Market = "Asia"

└─ Agent node: Asia Affiliate (child agent)

Each child agent has:
• A SharePoint knowledge source (.txt file) set to "At any time"
• Generative AI mode enabled
• No custom topics

My questions

Has anyone successfully implemented market-based child agent routing in Copilot Studio? If so, how did you set it up?

My current issue: when I select a market and ask a question, the child agent gets stuck in a loop — it keeps searching the knowledge source repeatedly (6+ times) but never returns an answer to the user. The knowledge file I'm using for testing is a short .txt file with minimal content, so it shouldn't be a size issue.

Would love to see a working example or any guidance on the correct architecture for this use case.

Categories:

Topic creation & management

General topics

Hi @TN-06050724-0,

from Microsoft docs the knowledge search loop you're seeing is a known behavior when the parent agent's orchestration doesn't receive a clear completion signal from the child agent. The child keeps being re-invoked because the parent isn't sure the task is done. This is confirmed in Microsoft's own documentation on child agent loops.

Three things to fix:

1. Child agent descriptions are critical. Microsoft docs explicitly state: "The parent agent uses subagent descriptions to decide routing. If descriptions are vague, identical, or inaccurate, the parent can't make good routing decisions." Make your child agent descriptions very explicit, for example: "Handles all questions from users who selected Europe as their market. Searches Europe-specific knowledge only." This prevents the parent from re-invoking the wrong agent.

2. Add explicit instructions to each child agent to signal completion. In each child agent's instructions, add: "After answering the user's question, end your response. Do not ask follow-up questions. Return control to the parent agent." Without this, the child doesn't send a completion signal and the parent keeps retrying.

3. Your routing architecture in Conversation Start may be the issue. Using condition nodes to route to child agents in Conversation Start can conflict with generative orchestration. Microsoft's confirmed pattern is: let the parent agent use generative orchestration to route to child agents based on their descriptions, rather than hard-coding the routing in a topic. Instead of the condition branch in Conversation Start, ask the market question in a topic, store the answer in a variable, then pass that as an input to the child agent so the child knows which market context to use.

If routing via topic is required, add the Agent node inside a topic (not Conversation Start) and make sure the topic ends cleanly with an End conversation or Go to another topic node after the Agent node.

Ref: https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/multi-agent-patterns

Ref: https://learn.microsoft.com/en-us/microsoft-copilot-studio/add-agent-child-agent

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube