Unanswered

Copilot agent in Teams showing error intermittently

(0) Share

Report

Posted on by JL-01070040-0

I've built a copilot agent using Sharepoint as its knowledge source, and deployed it into the Teams channel for others in the organisation to use via Microsoft ID and PAYG billing.

Everyone I shared it with can usually access it without any issues, but from time to time, on random days, some users - not all - would run into an error like this:

Sorry, something unexpected happened. We’re looking into it. Error code: SystemError. Conversation ID: a:1BLJn10fBLRArZNuBxdwL_gAS***. Time (UTC): 9/9/2025 10:55:47 PM.

Whenever this happens, I would ask them to clear the history of the agent, then use the initial link I shared with them to "force restart" it. This works every time, but it's annoying. Does anyone know how to stop this error message from showing up?

Categories:

General

I have the same question (1)

All responses (2)

Answers (0)

JL-01070040-0 2 on at

Like (0)

Report

Copilot agent in Teams showing error intermittently

Thanks Gracetonality! These are helpful tips. Can you tell me how do I schedule a refresh/restart of the agent in Teams?

Was this reply helpful? Yes No
Gracetonality 19 on at

Like (0)

Report
Copilot agent in Teams showing error intermittently

Thanks for sharing your experience! What you’re describing—random SystemError messages for some users—is something I’ve seen occasionally with Teams-deployed Copilot agents using SharePoint as a knowledge source. A few things to consider:

Session/Cache Issues: Clearing the agent history and forcing a restart works because it essentially resets the session. The errors often happen when the session state gets out of sync or expires.

Licensing/Permissions: Make sure all users consistently have access to the underlying SharePoint content and any Microsoft 365 license requirements. Sometimes the error only appears for users whose session or permissions have temporarily lapsed.

Concurrency/Load: If multiple users hit the agent at the same time, occasionally it may cause transient failures. PAYG billing agents can sometimes show random errors under load.

Error Logging & Feedback: Keep an eye on the Conversation IDs and timestamps when errors occur. You can log these and report them to Microsoft via the admin center or support—they’re helpful for debugging intermittent issues.

Potential Workarounds:

Encourage users to always start a new session if they hit an error.

If the agent is mission-critical, consider a scheduled “refresh” or restart” of the agent in Teams.

Check if your SharePoint library has any large files or complex permissions that could cause occasional lookup failures.

Unfortunately, there isn’t a 100% foolproof way to eliminate these random SystemErrors entirely—Microsoft sometimes updates the service behavior—but following the steps above usually reduces the frequency significantly.

1 people found this reply helpful.

Was this reply helpful? Yes No