web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Copilot Studio
Suggested Answer

SystemError

(0) ShareShare
ReportReport
Posted on by

Hi all,

We launched a Copilot Studio agent (internal HR assistant, deployed on the Microsoft Teams channel) ~10 days ago, and since go-live we've been getting an intermittent generic error shown to end users:

 

"An unexpected error has occurred. We're looking into it. Error code: SystemError. Conversation ID: 19:…@thread.v2. Time (UTC): …"

 

Details:

- 15 occurrences in 10 days, affecting multiple user
- Irregular — no clear pattern by topic or time of day
The agent is fully published; the same topics and generative answers work correctly when tested in the authoring canvas
No Application Insights connected yet, so I can't pull the server-side stack trace myself
- I have the conversation IDs + UTC timestamps on hand for anyone who needs them
 

This really looks like a service-side / backend issue rather than a config problem on my end.

Questions:

  1. Is anyone else seeing SystemError spikes on Teams-channel agents since roughly mid-June 2026? (possibly tied to a recent monthly rollout?)   
  2. Is this a recognized known issue right now?
  3. Any workaround to reduce the frequency while it's investigated, or is opening a support ticket the only path?



    Thanks in advance 🙏
I have the same question (0)
  • Suggested answer
    sannavajjala87 Profile Picture
    515 Super User 2026 Season 1 on at
    This looks like an intermittent service‑side issue, especially since it only happens in Teams and not in the test canvas. It’s likely related to channel/runtime instability or transient backend failures, not your configuration. There have been similar sporadic SystemError cases recently, often after service updates. There’s no guaranteed fix, but you can reduce impact by simplifying flows, adding basic retry/fallback logic, and enabling Application Insights for visibility. The best next step is to open a Microsoft support ticket with the conversation IDs and timestamps so they can investigate backend logs.
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Copilot Studio

#1
Valantis Profile Picture

Valantis 277

#2
11manish Profile Picture

11manish 206

#3
sannavajjala87 Profile Picture

sannavajjala87 156 Super User 2026 Season 1

Last 30 days Overall leaderboard