> For the complete documentation index, see [llms.txt](https://doc.threatreaper.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.threatreaper.ai/user-guide/troubleshooting_and_faq.md).

# Troubleshooting\_and\_FAQ

<details>

<summary>A module is missing from the sidebar</summary>

Not licensed, not enabled for your project, or your role lacks view permission. Ask your administrator. Try switching tenants.

</details>

<details>

<summary>"No tenant" or 403 right after sign-in</summary>

Your account is not a member of any active project. Ask an administrator to add you.

</details>

<details>

<summary>Sign-in blocked: account not activated</summary>

You have not finished the invitation. Use the email link; request a new one on the Set Password page if it expired.

</details>

<details>

<summary>Account locked</summary>

Too many failed sign-ins. Wait 10 minutes or ask an administrator.

</details>

<details>

<summary>Signed out unexpectedly</summary>

Inactivity timeout, another sign-in ended your session (single-session setting), or an administrator reset your password or removed you from the tenant.

</details>

<details>

<summary>Action refused: credits required</summary>

The module balance is too low. Ask an administrator to add credits.

</details>

<details>

<summary>Scan stays at "running"</summary>

Check Notifications for a failure message; for connector scans, verify the connector status in **Settings > Connectors**.

</details>

<details>

<summary>Discovery shows no local assets</summary>

The agent is offline or not registered. Check agent status (Admin Guide).

</details>

<details>

<summary>Everything shows zero</summary>

The selected project or date range has no data.

</details>

<details>

<summary>Search for a connector or setting finds nothing</summary>

Your role may hide it; ask an administrator.

</details>

<details>

<summary>Connector save fails with a validation error</summary>

A required field is missing or in the wrong format (for example, an Azure Tenant/Client ID must be a GUID, a GitHub token must start with `ghp_`/`gho_`/`ghs_`). Re-check [15.1](#151-before-you-start--what-youll-need) and the provider note in [15.3](#153-provider-specific-notes).

</details>

<details>

<summary>Connector shows "Inactive" or a module can't use it</summary>

The credential expired, was revoked, or lost permissions at the source system. Edit the connector and re-enter a valid credential (see [15.4](#154-managing-existing-connectors)).

</details>

<details>

<summary>New connector doesn't appear in a scan/policy dropdown</summary>

Refresh the page, confirm you're in the same project the connector was created in, and confirm your role can view connectors.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.threatreaper.ai/user-guide/troubleshooting_and_faq.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.