Power Platform Community Forum Thread Details

Hello,
I’m facing a persistent issue with one Copilot Studio agent in Power Platform.
Scope

Agent type: Copilot Studio (new experience)
Impact: Only one agent is affected
Other agents in the same environment are working correctly

Issue Description

When opening the agent in Copilot Studio:
- The page does not load (blank / stuck UI)
- No error message is displayed
When attempting to open the same agent from a test environment, the following message appears:

“Something went wrong. Try reloading the page. If the problem persists, contact your administrator.”

The failure occurs immediately when opening the agent, before any edit, test, or publish action.

Context

No identified changes prior to the issue:
- No known configuration change
- No license change
- No environment migration or rename
Issue started: March 6, 2026

Checks Already Done

Tried another browser → same behavior
Page reload → no improvement

Open Questions

No usable error details in the UI
Unclear whether this is:
- an agent-level corruption,
- a backend dependency issue,
- or a silent service degradation affecting a single agent

Question
Has anyone experienced:

a single Copilot Studio agent becoming inaccessible without a clear error, while others still work?
any known recovery steps or diagnostics for this scenario?

Any feedback or experience would be appreciated.
Hello,
I’m facing a persistent issue with one Copilot Studio agent in Power Platform.
Scope

Categories:

Autonomous agents

Common Causes

Agent-level corruption: Sometimes, the agent’s metadata or configuration becomes corrupted (e.g., due to a failed save, bad import, or backend glitch).
Orphaned references: The agent may reference a deleted or inaccessible resource (knowledge source, connection, environment variable, etc.).
Backend sync issue: Occasionally, backend services lose sync with the agent’s state, causing it to fail to load.

Recovery Steps & Diagnostics

Check Admin Center for Errors:

Go to Power Platform Admin Center → Monitor → Environment → View service health and logs for any related errors.
Export and Re-import (if possible):

If you can access the agent from the maker portal or via Power Platform CLI, try exporting it as a solution and re-importing into a new agent.
Sometimes, the export will fail—this confirms corruption.
Check for Orphaned Resources:

If you recently deleted or changed a knowledge source, connection, or environment variable, try restoring it.
Try Power Platform CLI:

Use the CLI to list and export agents. If the CLI fails on this agent, it’s likely a backend issue.