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 :
Power Platform Community / Forums / Copilot Studio / generic error using Te...
Copilot Studio
Suggested Answer

generic error using Teams Get Messages connector

(0) ShareShare
ReportReport
Posted on by 2
I'm trying to get messages from a specific channel in Teams using the Get Messages connector. I have no problems creating a Connection to Teams and adding the connector as a tool to my agent. The drop down to choose the Team and Channel are populated with correct values, which verifies that the connection to Teams is working. However, evert time I ask a question of the chat bot, it returns a generic "Error code: SystemError" message. I have enabled app insights logging and the same generic log appears there with no further details. I enabled logging in MS Graph to a Log Analytics workspace, and all of the requests logged there show a status of 200.
Can anyone suggest what might be causing the generic "systemerror" message, or where I can get more details about the internal error?
I have the same question (0)
  • Suggested answer
    Sayali-MSFT Profile Picture
    Microsoft Employee on at
    Hello,
    The “SystemError” when using the Teams Get messages action in Copilot Studio is usually caused by connector or runtime limitations rather than authentication or permission issues. The most common cause is using Private or Shared channels, which Copilot Studio can list but often cannot reliably retrieve messages from. Other frequent causes include large message payloads, delegated user-context access issues, and unsupported message types such as meeting system messages, Loop/Fluid content, Adaptive Cards, or rich previews, which may break the connector’s internal schema processing.
    Even though Microsoft Graph logs show successful 200 responses, the failure occurs inside the Copilot Studio runtime layer, which currently does not expose detailed diagnostics. Troubleshooting typically involves testing with a new standard channel containing only a few plain text messages, reducing the number of retrieved messages, verifying user access, or validating the same action in Power Automate to determine if the issue is Copilot Studio–specific. In many production scenarios, teams work around this limitation by using Microsoft Graph via a custom connector or Power Automate flow to retrieve and sanitize messages before returning them to the Copilot agent

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