Forum Discussion

Parth49's avatar
Parth49
Tin Contributor
Oct 22, 2026

Copilot Studio agent behaves differently in Teams and the test pane

Hello,

We have built a topic-based agent in Microsoft Copilot Studio that uses SharePoint as a knowledge source and is published to Microsoft Teams.

We are seeing the following behavior:

  1. The agent sometimes stops responding in Teams.
  2. To make it respond again, we need to use commands such as:

/debug clearstate

/debug clearhistory

/debug conversationid

      3. One of our topics contains a Question node asking whether the user’s query was resolved.

      4. The question and its options appear correctly in the Copilot Studio evaluation/test pane.

      5. However, the same question never appears when the agent is used in Teams.

Has anyone experienced similar behavior?

Any troubleshooting guidance would be helpful.

copilot studio
evaluation
knowledge grounding

2 Replies

  • Jamony's avatar
    Jamony
    MCT
    Nov 08, 2026

    The missing “was this resolved?” question and the Teams session recovering after a reset make retained conversation state worth checking. They do not establish a rendering defect.

     

    For a standard-harness agent, open that Question node's Properties > Question behavior and inspect Skip behavior. A question can be skipped when its variable already has a value. Select Ask every time if this confirmation must appear on every pass, then publish and test the route in Teams.

     

    For the intermittent silence, Microsoft's Teams deployment guidance recommends an inactivity-triggered topic that clears session variables/history and ends the conversation. Add a version marker so you can confirm Teams is using the published logic. Test both fresh and long-running sessions.

     

    If it still fails, retain the Conversation ID, Agent ID, reproduction time and steps for Microsoft Support. For SharePoint knowledge requiring user authentication, confirm you are testing a supported 1:1 chat.

  • SK_19's avatar
    SK_19
    Copper Contributor
    Oct 22, 2026

    Republish the agent and force a Teams channel refresh (remove/re-add in Teams)

    Enable Generative Answers fallback + check topic trigger priority order

    Validate Question node adaptive card rendering for Teams channel compatibility

    Add Power Platform admin-level session timeout + state persistence config

    Set up Application Insights logging to catch where Teams drops the dialog