docs/src/content/docs/en/troubleshooting.md
A: Service status, agent launch method, Agent Profiles application status, and effect scope all affect whether the agent goes through CCR.
A: Request logs show request model, resolved provider, and resolved model. The Routing Config page contains default routing, rule order, match conditions, and fallback.
A: Related fields include API Key, credential enabled state, Base URL, protocol, and extra request headers. The provider page provides model connectivity checks.
model not found?A: The provider model list, the model selected by routing, and the model in Agent Profiles can all affect model not found.
A: Related information includes Fusion tool enabled state, Vision model or search-service key, MCP Discover tools, and timeout settings.
A: Request logs record duration and error information. Upstream latency, Fusion tool duration, and timeout settings can also affect timeout behavior.
A: Request logs support filtering by model, provider, or credential, and show token composition, request-body size, and the final model used.
A: Request logs support filtering by credential. A credential's quota, permission, and provider-side account state can all affect whether a single key is usable.
A: Related information includes the Bot switch, message-forwarding settings, platform token, callback configuration, and whether the agent was opened from CCR.
A: Open Settings → Logs & Observability and confirm Request logs and Agent observability are enabled, then start a new agent task. The observability panel records steps, tool calls, tool results, and duration during new agent execution.