> For the complete documentation index, see [llms.txt](https://replai-1.gitbook.io/replai-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://replai-1.gitbook.io/replai-docs/faq-and-troubleshooting/general-troubleshooting.md).

# General troubleshooting

## General troubleshooting

Use this page when the assistant is not behaving as expected.

### Start here

{% stepper %}
{% step %}

### Check AI setup

Make sure the assistant has a valid AI setup.
{% endstep %}

{% step %}

### Check assistant status

Confirm the assistant is active and not paused at the limit.
{% endstep %}

{% step %}

### Check widget setup

Verify the widget is enabled and the domain is allowed.
{% endstep %}

{% step %}

### Check source freshness

Review sync status, source scope, and handoff setup.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Most failures come from missing AI setup, paused assistants, bad domain scope, or stale sources.
{% endhint %}

<details>

<summary>The assistant does not answer at all</summary>

Check whether the assistant has a valid AI setup.

Also confirm it is not paused and has not reached a paused monthly limit.

</details>

<details>

<summary>The widget does not load</summary>

Check that the widget is enabled, the script is installed, and the domain is allowed.

</details>

<details>

<summary>Visitors see an unavailable message</summary>

This usually means the assistant is paused or new conversations are paused at the monthly limit.

</details>

<details>

<summary>Answers are weak or off-target</summary>

Tighten source scope, remove noisy pages, and review the cited content first.

</details>

<details>

<summary>Content updates are delayed</summary>

Check the selected sync schedule or run a manual sync.

</details>

<details>

<summary>Human handoff fails</summary>

Confirm the assistant is on **Live** and that seats and queue coverage are set up.

</details>

### See also

* [Troubleshooting connectors](/replai-docs/connectors-sources/troubleshooting-connectors.md)
* [Getting help](/replai-docs/faq-and-troubleshooting/getting-help.md)
* [FAQ](/replai-docs/faq-and-troubleshooting/faq.md)
* [Live tier](/replai-docs/features-by-tier/live-tier.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://replai-1.gitbook.io/replai-docs/faq-and-troubleshooting/general-troubleshooting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.