Support
Start with Troubleshooting for common access, timeout, waiting-action, and evidence issues.
When you report a client issue, include the client version, operation name, and a minimal reproduction.
Redact API keys, customer data, and private run content from public issues.
An agent list or trajectory does not load
Retry the failed view and check that the intended project is selected. For older work, check the time range and the managed-run history in Conversations. A run can stay visible while its trajectory is unavailable or incomplete.
A loading error does not mean your agents or runs were deleted. Do not create a duplicate agent, rerun work, or upload the same run to recover a failed read.
If the problem persists, send support these details through a private support channel:
- The operation
- Approximate time and time zone
- Client version
- The relevant run ID
Do not include credentials or private trajectory content in public issue reports.