Logs
Logs are detailed records of every time an agent runs. They show you exactly what happened during each execution, helping you understand what your agents are doing and troubleshoot any issues.
Viewing Logs
To see the execution history for an agent, open the agent page and click the Logs button (list icon) in the header. You'll see a list of all runs, with the most recent at the top.
Each log entry shows key information at a glance:
- State: An icon indicating whether the run is still running, completed successfully, encountered an error, or was stopped
- Summary: A brief description of what happened or the current step if still running
- Duration: How long the run took (updates in real-time for running logs)
- Date: When the run started
Click on any log entry to see the full execution details. Use Load More at the bottom of the list to see older logs.
Understanding Log States
Logs can be in one of four states, each indicating where the agent is in its execution cycle:
- running: The agent is currently executing and the log updates in real-time
- done: The agent completed successfully
- error: The agent encountered an error and stopped
- stopped: The agent was manually stopped
Log Details
When you open a log, you'll see a timeline of everything that happened during the run. The timeline includes several types of information:
- Steps: Each major phase of execution is shown as a collapsible section. Click to expand and see detailed messages for that step.
- Documents: When your agent creates a document, it appears in the timeline with a link to open it.
- Errors: If something goes wrong, the error message is shown in red. You can click Fix This to open the agent's chat with the error details, making it easy to ask for a fix.
The timeline shows how long each step took, helping you understand where your agent spends its time.
Controlling What Gets Logged
You can control what is logged when you create or edit an agent using the chat interface. When you describe what you want an agent to do, you can specify what information should be logged, how detailed the logs should be, and what messages should appear at each step.