Users would randomly run into this error "Sorry, something unexpected happened. We're looking into it. Error code: SystemError"

SystemError is a catch-all error for an unexpected failure. In Copilot Studio, it usually means a transient infrastructure problem, an unexpected internal failure, or a condition that needs further investigation.

For this specific pattern where it appears randomly and then sometimes works again later, the supported troubleshooting path is:

1. Retry the request.
   • SYSTEM_ERROR can be transient, so a later retry may succeed.
2. Capture the conversation details when it fails.
   • Record the Conversation ID shown in the error.
   • Record the time of failure (UTC).
3. Use the activity trace if available.
   • The activity trace is the recommended place to get the conversation ID and debug details for agent failures.
4. If the problem persists, contact support.
   • Provide the captured conversation ID and failure time.
5. If multiple users are affected at the same time, have an administrator check the Microsoft 365 service health dashboard.

Also, in Copilot Studio guidance, SYSTEM_ERROR is classified as an error where retrying sometimes helps, and the next step after retry is support.

The browser or PC restart is not identified as the documented fix for SYSTEM_ERROR. The documented actions are retry, collect trace details, and escalate with the conversation ID and timestamp.

• Error codes reference for agents
• Error codes reference for agents
• Understand error codes