Inspect execution and troubleshoot¶
During execution, the conversation displays model calls, runtime preparation, and tool progress. Use these to distinguish work in progress, failed calls, and completed answers that do not meet your requirements.
Check normal execution¶
After sending, confirm that processing starts.
For files or tools, check whether the relevant calls return results or errors.
To interrupt execution, select the stop button or press Esc.
Review the answer, its evidence, and any actual output files or external results.
Sidebar processing and unread-completion indicators show conversation progress. They do not establish that the answer is correct or that an external action succeeded.
Use developer mode for diagnosis¶
Enable the page’s developer-mode switch to inspect the execution trace and call details. Expand a relevant tool record and review its name, parameters, result, and error. The execution view may also show elapsed time, token use, and cache information. You do not need this mode for ordinary tasks.
For a knowledge-based answer, inspect the retrieval call’s returned passages and compare them with the answer. This helps establish whether the agent actually used the source material.
Diagnose common problems¶
Problem |
Check first |
|---|---|
No knowledge-base retrieval |
Agent binding, completed file processing, and skill restrictions on external sources |
A tool was not called |
Agent binding, tool connection, and whether the task requires the tool |
Authentication or permission error |
Credentials, target-resource permissions, and credential expiry |
Network timeout |
Tool-service reachability, environment networking tools, and domain allowlist |
Text says an object was created but it is absent from the list |
Pending candidate confirmation and the actual saved object |
Changes appear not to apply |
Reopen details to verify saving, then start a new conversation from the target agent |
When reporting an issue, include the workspace, conversation entry, operation time, target resource, reproduction steps, and error. Avoid exposing complete credentials in screenshots.