Copilot Studio: After “End All Topics”, New User Input Does Not Trigger the Expected Topic and Routes to a Different Source

Question

Hi everyone, I’m facing an issue in Copilot Studio with how topics are triggered after completing a conversation flow.

I currently have two topics configured:

Topic A – This is the initial topic that should trigger when the user starts with a new message.

Topic B – This is the operational topic that handles specific workflow logic.

My expected flow is:

I send a message → Topic B triggers and completes successfully.

At the end of Topic B, I use End all topics (not End conversation).

After that, when I type a new message that should activate Topic A, it should trigger normally.

The issue: After ending the previous topic using End all topics, when I type a new message meant to trigger Topic A, the system is responding from a different source, instead of activating the correct topic. It seems to be bypassing Topic A entirely.

This behavior was working correctly just a few days ago, but now it has changed without any modifications on my side.

Has anyone else encountered this issue? Any insights on what might be causing this behavior or how to fix it would be very helpful.

Thank you!Hi everyone,

I’m facing an issue in Copilot Studio with how topics are triggered after completing a conversation flow.

I currently have two topics configured:

Topic A – This is the initial topic that should trigger when the user starts with a new message.

Topic B – This is the operational topic that handles specific workflow logic.

My expected flow is:

I send a message → Topic B triggers and completes successfully.

At the end of Topic B, I use End all topics (not End conversation).

After that, when I type a new message that should activate Topic A, it should trigger normally.

The issue:
After ending the previous topic using End all topics, when I type a new message meant to trigger Topic A, the system is responding from a different source, instead of activating the correct topic. It seems to be bypassing Topic A entirely.

This behavior was working correctly just a few days ago, but now it has changed without any modifications on my side.

Has anyone else encountered this issue? Any insights on what might be causing this behavior or how to fix it would be very helpful.

Thank you!

Answer 1

Hello Aniket Thorat,
“End all topics” stops all active topics but does not clear global variables, which can cause the next message to route incorrectly. Residual variables, system topics, or generative orchestration can override expected triggers.
The recommended fix is to add Clear all variables (and often End conversation) before “End all topics” to fully reset context. Also verify topic triggers, orchestration settings, and test in classic mode to rule out AI-based routing issues.
Reference Document-
1.https://learn.microsoft.com/en-us/microsoft-copilot-studio/authoring-topic-management?tabs=webApp