AI Agent Deployed on MS Teams returns SystemError

Janettt 20 Reputation points
2026-04-27T07:52:20.24+00:00

Hello everyone,

I am seeking assistance with an issue regarding an AI Agent (built via Copilot Studio) that I deployed in Microsoft Teams 2 weeks ago and shared with a select group of users in my organization.

The Issue:
Initially, the agent functioned perfectly. However, it recently began returning the following error for approximately 30% of the users:

"Sorry, something unexpected happened. We’re looking into it. Error code: SystemError. Conversation ID: [removed for privacy]" Time(UTC):[removed for privacy]

Once a user encounters this error, the bot seems to enter a loop. If the user attempts to reset the interaction by typing basic commands like "hi" or "start over," the agent fails to respond as intended and continuously outputs the exact same error message and Conversation ID.

Troubleshooting Steps Taken:

  • Uninstalled and reinstalled the AI agent for the affected users.
  • Cleared the MS Teams application cache.

Unfortunately, neither of these steps resolved the issue.

Has anyone encountered a similar looping SystemError with their deployed agents, or are there specific configurations or logs I should review to break this error loop? Any guidance would be greatly appreciated.

Microsoft Copilot | Microsoft 365 Copilot | Development
0 comments No comments

Answer accepted by question author
Sayali-MSFT 6,426 Reputation points Microsoft External Staff Moderator
2026-04-27T08:42:29.5966667+00:00

Hello Janettt ,
The issue is most likely caused by a combination of corrupted conversation state and user-specific execution failures in your Copilot Studio agent. Since only about 30% of users are affected and the error repeats with the same conversation ID, the bot is getting stuck in a broken session loop where even simple inputs fail. This is often triggered by failures in flows, prompts (like Claude), or connectors due to permission or authentication differences between users.

To resolve it, focus on forcing a new conversation ID, checking Copilot Studio analytics to identify the failing topic or node, validating user permissions, and reviewing Power Automate run logs. In many cases, isolating the failing component or republishing the agent helps break the error loop.

Reference Document-
1.https://learn.microsoft.com/en-us/microsoft-copilot-studio/analytics-overview
2.https://learn.microsoft.com/en-us/power-automate/fix-flow-failures
3.https://github.com/Azure/Copilot-Studio-and-Azure/blob/main/docs/troubleshooting/README.md

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.