Building and customizing solutions using Microsoft 365 Copilot APIs and tools
SYSTEM_ERROR is a catch-all error code in Copilot Studio for an unexpected failure that does not match a more specific error category. It usually means a transient infrastructure problem, an unexpected internal failure, or a condition that needs engineering investigation.
It does not mean “just wait and do nothing” in every case.
What it means in practice:
- Retry first. This error can be transient, so trying the request again may work.
- If it keeps happening, collect details and escalate. Capture the conversation ID from the activity trace and the time of failure, then contact support.
- If many users are affected at once, have an administrator check the Microsoft 365 service health dashboard.
About “who’s we”:
- The product message is referring to the Microsoft service side, not to an automatic guarantee that the issue will resolve on its own without any follow-up.
- The official guidance is to retry, then investigate/escalate if persistent.
A useful way to think about it:
- One-off failure: retrying later might fix it.
- Repeated failure on the same scenario: treat it as something that needs investigation, not passive waiting.
If this happens while testing the agent, error details can also appear in the Preview tab, Preview history, Activity trace, and Evaluate results. In the classic troubleshooting guidance, agent makers can also use the test pane for more context and the Topic checker panel to validate the agent.