Troubleshooting

Start in Operate the Runtime Console to distinguish live server state from the browser projection. Then follow the boundary that matches the symptom:

Symptom	Current guide
401, JWKS failure, or provider conflict	Authenticate Requests
Provider key unavailable or credential API returns 503	Manage Provider Credentials
Policy denial or unexpected permit behavior	Apply Governance Policies
Tool call waits or rejects	Resolve Tool Approvals
Stream disconnect, missed live update, or stale browser state	Understand Realtime State
Empty metrics, readiness failure, or missing traces	Observe the Runtime
Prompt caching setting fails to load, or cache reads stay at zero	Configure Prompt Caching
Cost is absent or differs from provider totals	Interpret Cost and Budgets
Datastore lock, forced exit, backup, or restore question	Recover and Shut Down

Record the active profile, source revision, exact request or command, status, and relevant redacted logs. Do not include credentials, private keys, or raw user/session payloads in a public issue.