> This page is also available as Markdown: append .md to its URL. The full index of Sikaru docs is at https://docs.sikaru.ai/llms.txt. Code examples use only operations from the public API reference at https://docs.sikaru.ai/api-reference.

# Support

Start with [Troubleshooting](/help/troubleshooting) for common access, timeout, waiting-action, and evidence issues.

| Need                                                       | Where to go                                                      |
| ---------------------------------------------------------- | ---------------------------------------------------------------- |
| Common access, timeout, waiting-action, or evidence issues | [Troubleshooting](/help/troubleshooting)                         |
| Account or service questions                               | [Sikaru support](mailto:support@sikaru.ai)                       |
| SDK issues                                                 | [SDK repository](https://github.com/aadi-labs/sikaru-sdk/issues) |
| CLI issues                                                 | [CLI repository](https://github.com/aadi-labs/sikaru-cli/issues) |

When you report a client issue, include the client version, operation name, and a minimal reproduction.

> **Warning**
>
> 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.