Copilot studio agent stops responding in Teams channel

(2) Share

Report

Posted on by YM-27122000-0

I created a Copilot Studio agent and enabled the Teams channel, published. It provides responses, then after a while it stops responding in Teams. I have no way to start a new conversation. So had to remove the channel, re-enable again.

When it stops responding, it doesn't respond to any users using it. This happens with other Copilot agents.

I cannot deploy this to production if it's unstable like this. If the product is not stable, will use Amazon or other products. It's too bad, it has many good things but it needs to be stable in order to be prod ready. Please fix it.

Categories:

General topics

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Suggested answer

11manish 2,983 on at

Like (0)

Report
Copy link

Link copied!

If multiple Copilot Studio agents consistently become unresponsive in Teams while remaining functional elsewhere, the issue is likely related to the Teams

channel integration, environment health, or a platform-side service issue. Before moving to production, it's worth validating whether this is a tenant-specific

problem or a broader service issue with Microsoft support, as repeatedly removing and re-adding the channel is not a sustainable production solution.

Was this reply helpful? Yes No
Suggested answer

Haque 3,462 on at

Like (1)

Report
Copy link

Link copied!

Hi @YM-27122000-0,

Enable and Monitor Telemetry and Logs: Enable detailed logging and telemetry for your Copilot Studio agent to capture errors or warnings when the agent stops responding. This helps identify root causes.

Use Fallback or Timeout Handling in Agent Flows: Design your agent flows to handle timeouts gracefully and provide fallback messages or retry logic.

Engage Microsoft Support: Since this impacts production readiness, open a support ticket with Microsoft to investigate backend service logs and platform-level issues.

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No
Suggested answer

Valantis 6,456 on at

Like (1)

Report
Copy link

Link copied!

Hi @YM-27122000-0,

few things to do is republish only if that doesnt work then what you already did remove and add the channel.

also so that your agent doesnt brake alwys use a topic to clear the variables so always start with clean variables when the convo start.

you can see here to set it up: https://valantisond365.com/handle-abandoned-chats-in-copilot-studio/ this helped me with my help that i have a similar issue.

let me know if that work out for you.

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

Was this reply helpful? Yes No
Suggested answer

RaghavMishra 216 on at

Like (0)

Report
Copy link

Link copied!
Hi @YM-27122000-0,

Why this happens

This is expected Teams-channel behavior rather than the agent being broken. Teams conversations persist across days without an automatic reset. Unlike Web Chat, the ConversationStart event fires only the first time the agent is added, and reinstalling the app doesn't retrigger it. Over a long-lived thread this leads to stale context, connector token expiration, and accumulated messages exceeding model limits - which is why the agent appears to stop responding and you can't cleanly start a new conversation.

Recommended fixes

Implement inactivity resets in your agent:

Create a topic that uses the The user is inactive for a while trigger.

Add Clear variable values nodes to remove session variables and conversation history (prevents context overflow).

End the conversation and mark the session as resolved.

Offer a self-service reset command: tell users they can type /debug clearstate, which clears conversation state, removes cached connector information, reauthenticates connectors, and loads the latest version of the agent. This is the documented fix when the bot seems "stuck," connector authentication has expired, or behavior is inconsistent.

Because ConversationStart only fires once, treat your Greeting topic as the effective initialization point and prompt users to say "hello" to re-run startup logic.

Reference

Deploy agents in Microsoft Teams - Microsoft Copilot Studio

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