Error ContextTokenLimitExceeded in Microsoft Teams

Question

ContextTokenLimitExceeded gets permanently stuck in a Teams 1:1 chat with a Copilot Studio agent and cannot be cleared. After a long conversation the agent returns this error; "Start over" and clearing chat history do NOT reset the context (same error returns immediately), and removing the agent app fails with "There was an issue while trying to remove... Please try again."

The agent is healthy — it works fine in the Copilot Studio Test pane (fresh session) — so the issue is that the Teams conversation thread cannot be flushed. Reproducible across two separate accounts. Sample Conversation Id: <PII removed> (UTC 2026-07-23T07:36:13.749Z).

Expected: "Start over"/clearing the chat should reset the conversation context. Actual: no working recovery path. Please fix the reset behavior and the failing app removal.

Answer 1

Hi @Ilia Stepanov

Please note that we're not Microsoft Support, this is a user-to-user community forum. Moderators here don't have access to your environment or Microsoft's backend systems, so we can only provide guidance based on public documentation and community experience. And since this is a public platform, and we will modify your question to hide your personal information in the description. Kindly ensure that you hide any personal or organizational information the next time you post an error or other details to protect personal data.

Thank you for the detailed information and the screenshots.

Based on what you've shared, the behavior does not appear to be expected. Normally, selecting Start over should initiate a new conversation context. If the conversation continues to return ContextTokenLimitExceeded immediately afterward, even after clearing the chat history, it suggests that the previous conversation state may not have been reset successfully.

Additionally, the inability to remove the agent from the Teams chat may indicate a related issue with the conversation or app state, although it is difficult to determine from the forum whether both behaviors stem from the same underlying cause.

Since the issue is reproducible across multiple accounts and the agent functions normally in the Copilot Studio Test pane, this is likely something that requires investigation from the service side. As forum moderators do not have access to backend logs or conversation state, I recommend opening a support ticket with Microsoft. Please include the Conversation ID, the UTC timestamp, and the screenshots you shared, as these will help the engineering team correlate the service logs and investigate why the Teams conversation cannot be reset.

Thank you for your understanding.

---

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

Answer 2

@Ilia Stepanov I am also facing the same issue. Do you think submitting a ticket is the ultimate solution of this?

Thanks,