Copilot Studio Agent remains stuck with ContextTokenLimitExceeded after /debug clearstate

Question

Copilot Studio Agent remains stuck with ContextTokenLimitExceeded after /debug clearstate

Nguyen Tran Minh Tu 0

A Copilot Studio agent deployed to Microsoft Teams is permanently stuck with ContextTokenLimitExceeded in an existing 1:1 conversation.

Issue scope:

The issue occurs only in the existing Microsoft Teams 1:1 chat.
The agent works correctly in a new Copilot Studio Test session.
The Helpdesk Core API connector also works normally in the Test session.

Troubleshooting performed:

Sent “Start over” in the Teams conversation.
Sent the command /debug clearstate.
The agent returned: “The state of conversation was cleared successfully.”
Sent a new short message: “xin chào”.
The agent immediately returned ContextTokenLimitExceeded again.
The new error still showed the same Conversation ID.
Started a new Copilot Studio Test session and confirmed that the agent works normally.
Confirmed that the Helpdesk Core API connector successfully retrieves ticket data in the Test session.

Error code:

ContextTokenLimitExceeded

Conversation ID starts with:

a:1yBlGghDZ15I...

Latest UTC timestamp:

2026-09-11T02:07:45.093Z

Observed behavior:

/debug clearstate reports success.
The following message still uses the same Conversation ID.
ContextTokenLimitExceeded is returned immediately.
The conversation context does not appear to be recreated.
A new Copilot Studio Test session works normally.

Expected behavior:

After “Start over” or /debug clearstate, the following message should begin with a fresh conversation context and should not reuse the context that exceeded the token limit.

Impact:

The affected user cannot continue using the agent in the existing Microsoft Teams 1:1 conversation.

Questions:

How can Microsoft Teams be forced to create a new Copilot Studio conversation session?
Is there a supported way to permanently clear or recreate the stuck conversation state?
Why does /debug clearstate report success while the same Conversation ID continues to be used?

Please advise whether this behavior requires investigation or cleanup from the Microsoft service side.

0 comments

1 answer

Your answer

Answer 1

Sayali-MSFT 6,476 Microsoft External Staff Moderator

Hello Nguyen Tran Minh Tu •
This appears to be a stuck persistent conversation state in Microsoft Teams, rather than an issue with the agent or the Helpdesk Core API connector.

The Start over and /debug clearstate options can clear runtime state, but they don’t necessarily create a new Teams 1:1 conversation or Conversation ID. Since the same Conversation ID is reused and ContextTokenLimitExceeded returns immediately, the conversation state may not have been fully cleared. Teams conversations are persistent, unlike a new Copilot Studio Test session.
https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/deploy-agent-teams
https://learn.microsoft.com/en-us/troubleshoot/power-platform/copilot-studio/authoring/error-codes?tabs=webApp

There doesn’t appear to be a supported user-side method to force a new Conversation ID for an existing Teams 1:1 chat. Since the agent and connector work correctly in a fresh Test session, this likely requires Microsoft service-side investigation or cleanup.

Could you please share the below details for investigation purpose:

Full Conversation ID
UTC timestamp: 2026-09-11T02:07:45.093Z
Error: ContextTokenLimitExceeded
Confirmation that /debug clearstate succeeded but the same Conversation ID was reused
Teams and Copilot Studio Test session comparison
Agent, environment, tenant, and affected-user details

As a temporary workaround, you can test with another user or conversation scope, but the affected 1:1 thread may remain unusable until the backend state is investigated.

Nguyen Tran Minh Tu 0 Reputation points

2026-09-11T06:03:47.5533333+00:00
Hello Sayali,

Thank you for confirming that this appears to be a stuck persistent conversation state in Microsoft Teams.

Here are the requested details:

Error:

ContextTokenLimitExceeded

UTC timestamp:

2026-09-11T02:07:45.093Z

Clear-state confirmation:

The /debug clearstate command returned:

“The state of conversation was cleared successfully.”

However, the next short message immediately returned ContextTokenLimitExceeded, and the same Conversation ID was reused.

Test comparison:

The issue occurs in the existing Microsoft Teams 1:1 conversation.

The agent works correctly in a fresh Copilot Studio Test session.

The Helpdesk Core API connector also works correctly in the fresh Test session.

Clearing the Teams desktop cache did not resolve the issue.

The same Teams 1:1 Conversation ID continues to be reused.

Agent:

Agent AI for IT Operation

Affected scope:

Microsoft Teams 1:1 chat

Affected user:

The user who created this question.

Because this is a public forum, I prefer not to post the full Conversation ID, environment ID, tenant information, or user email publicly.

Could you please provide a secure/private method for sharing the full Conversation ID and the remaining environment and affected-user details for Microsoft service-side investigation?

The affected Teams 1:1 conversation is still unusable.

Thank you.
Nguyen Tran Minh Tu 0 Reputation points

2026-09-11T06:11:49.18+00:00

Additional information:

I tested with another user in the same tenant.

The same agent responds normally for that user in Microsoft Teams.

The agent also works correctly in a fresh Copilot Studio Test session.

This confirms the issue is isolated to my existing Teams 1:1 conversation with the agent and does not affect the agent globally.

The affected conversation remains unusable and continues to return ContextTokenLimitExceeded.