Copilot Studio Topic to Agent Routing
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- ai-infra-agents
Research direction
Start in Copilot Studio Agent > Topic > System Prompt and reproduce the Architecture Analysis routing flow described in the issue. Verify whether the orchestrator routes input to the published subagent and whether the routed agent produces output in the workflow; done means the subagent and its results appear instead of only the custom response.
Written by the indexing model from the issue text.
Description
What sample tool are you using?
We're using CoPilot Studio Agent Topic to Agent routing.
Describe the bug
We have an orchestrator A2A framework set up for our use case. When trying to route a topic, say, conversation start, to one of the workflow with our sample agent, there are no output coming from the orchestrator agent, nor will there be any outputs coming from the agent the topic is routed to.
Below is an example:
Here's the topic it was route to with the agent inside:
To Reproduce
Steps to reproduce the behavior:
- Go to CoPilot Studio Agent -> Topic -> System Prompt
- For setting up "Architecture Analysis" Topic, please see the screenshot above, add a published copilot studio agent inside the topic.
- Click on '+' for adding another Topic created with Agent inside, as seen in the example "Architecture Analysis"
- Once topic configured, start a new session in the copilot studio orchestrator agent, and ask the question in image 1, or any general question that should invoke the orchestrator agent to route to the assistant subagent.
- There is no output at all, despite having output variable configured, nor is there any results shown in the process flow.
Expected behavior
We expect the subagent to be routed to, and accept in the input from the orchestrator agent in the workflow diagram.
Screenshots
Additional context
A2A conversation with Topic seems to be a newer feature as I don't recall seeing this a few days before. However, we were not able to utilize any of the said features it can provide.
- Dominant language
- TypeScript
- Stars
- 797
- Forks
- 491
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/CopilotStudioSamples
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
SharePointSSOComponent
microsoft/CopilotStudioSamples#537 · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/CopilotStudioSamples#532 · 1 comment ·
-
Unable to Deploy SPFx Agent to a Single SharePoint Site (Works Only with Tenant-Wide Deployment) Open
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/CopilotStudioSamples#531 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in microsoft/CopilotStudioSamples
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·