Agent unable to find topic in New Experience

(0) Share

Report

Posted on by ET-12060849-0

In the new designer, when I use connected agent / publish in teams, the agent always reply “Sorry, I am not able to find a related topic. Can you rephrase and try again?”

However, there no longer are any topics in the new experience when creating an agent. There are skills. And when I test in preview pane, the individual agent works exactly as intended. But when connected or published, they always reply the in the given example above.

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

RaghavMishra 185 on at

Like (0)

Report
Copy link

Link copied!
Hi there,

Great question - this behavior is expected once you understand how the new designer works compared to the classic one.

Why it happens

In the new experience, newly created agents use generative orchestration by default (instead of classic orchestration). The difference matters here:

Classic orchestration triggers the topic whose trigger phrases most closely match what the user typed.

Generative orchestration dynamically chooses the best tools, knowledge, topics, and connected/child agents to answer - and it makes that choice primarily from the description you give each item.

So when a connected or published agent keeps replying “Sorry, I am not able to find a related topic. Can you rephrase and try again?”, it usually means orchestration couldn’t confidently match the request to one of your topics/tools/agents - most often because the descriptions are missing or too generic. (In the preview/test pane the individual agent works because you’re testing it directly, not going through the parent agent’s orchestration.)

What to check / do

Confirm the orchestration mode on the agent (Settings → Orchestration / generative AI). Note: if an admin turned off generative orchestration for the environment, agents there can only use classic orchestration.

Add a high-quality, specific description to every topic, tool, knowledge source, and connected/child agent. Good descriptions are what let the agent pick the right one.

For topics, make sure they’re enabled for generative orchestration once you turn it on.

Test phrasing variations in the test pane to confirm the right item is selected and chained.

References (Microsoft Learn)

Orchestrate agent behavior with generative AI

Add other agents overview

Found this helpful? Please mark ✅ "Does this answer your question?" so others searching for the same issue can find it quickly. A 👍 on "Was this reply helpful?" or a ♥ Like is also much appreciated!

Raghav Mishra - LinkedIn | PowerAI Labs

Was this reply helpful? Yes No
Suggested answer

11manish 2,837 on at

Like (0)

Report
Copy link

Link copied!
Since the agent works correctly in the preview pane, the underlying logic, knowledge, and skills are likely functioning correctly.

The most probable causes are:

Connected agent routing/orchestration issues

Skill exposure or discovery configuration

Publishing synchronization problems

A recent Copilot Studio regression affecting connected agents

I would start by publishing the child agent directly to Teams, verifying it works independently, then reviewing the connected agent configuration, skill

descriptions, and orchestration settings. If the issue persists across multiple agents, it may be worth checking recent Microsoft advisories or opening a support

ticket, as there have been occasional regressions in the connected-agent framework as Copilot Studio continues transitioning from the legacy topic-based model

to the new agent architecture.

Was this reply helpful? Yes No
AndrianaO 238 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi @ET-12060849-0! I've seen the same error message when I tried to trigger the agent built in New Experience with "Execute Copilot" action in Power Automate. I didn't even try to publish that agent, so maybe the message we get is just a temporary placeholder and not the indication that we need to fix unexisting topics.

In my opinion, it's a temporary technical issue that Microsoft will resolve in some time. New Experience is very new, so I expect it to have some problems here and there at the beginning.

Was this reply helpful? Yes No