Troubleshooting
Performance & cost
Diagnose unexpected cost increases and slow or crashing long runs.
Run cost increased unexpectedly
Common drivers:
| Driver | What to check |
|---|---|
| Oversized images or logs | Very large screen captures or log files raise the token count per step. |
| Retry loops | A failing step the agent retries many times multiplies cost. Look for high step counts on single actions in the run report. |
Open the run report and check the token count per step, the costliest steps are usually the ones to optimize. For a cross-run view, see the Usage dashboard.
Run got slower or crashed during a very long execution
Log and trace files grow continuously over a run. Very large files can exhaust memory or significantly slow the host machine.
Mitigations:
- Keep test cases short and focused, split a large suite into smaller cases, each producing its own report.
- Archive or delete old run folders under
agent_workspace/in your project periodically. - If a run must be long, monitor disk and memory usage on the AgentOS host and set up log rotation if your OS supports it.