> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/no-code-experiences/chat-experiences/troubleshooting.md).

# Troubleshoot Chat Experiences

Find the chat experience symptom you are seeing, from a room that will not connect to a transcript that will not download, and the page that answers it.

Chat Experiences reports what is wrong where it happens: the message box says why it is locked, the character picker says why a character will not join, and anything else is reported on the page you were working on. Start from what you can see on screen, and these pages tell you what it means and what clears it.

### Where each symptom is answered

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>The room will not connect</strong><br>Characters that never finish joining, an experience that will not open, and a character the picker will not add.</td><td><a href="/api-docs/no-code-experiences/chat-experiences/troubleshooting/room-will-not-connect.md">The room will not connect</a></td></tr><tr><td><strong>You cannot send a message</strong><br>Every reason the message box is locked, in the room's own words, and what clears each one.</td><td><a href="/api-docs/no-code-experiences/chat-experiences/troubleshooting/composer-is-locked.md">You cannot send a message</a></td></tr><tr><td><strong>Briefs and transcripts</strong><br>A brief that cannot be edited, an experience that will not be created, and a session that will not open or a transcript that will not download.</td><td><a href="/api-docs/no-code-experiences/chat-experiences/troubleshooting/briefs-and-transcripts.md">Briefs and transcripts</a></td></tr><tr><td><strong>File limits reference</strong><br>A file the room will not attach, an attachment taken off a message for length, and text cut short before it reaches the characters.</td><td><a href="/api-docs/no-code-experiences/chat-experiences/share-files-with-the-room/file-limits-reference.md">File limits reference</a></td></tr></tbody></table>

### Behavior that is not a fault

Five things that look like faults are how a chat experience works:

| What you see                                | Why                                                                                          | Where it is explained                                                                                                                                        |
| ------------------------------------------- | -------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| The room opens with nobody in it            | Characters are seated for each session, and the roster does not carry over from the last one | [Sessions and transcripts](/api-docs/no-code-experiences/chat-experiences/sessions-and-transcripts.md#what-carries-over-to-the-next-session)                 |
| A character said nothing at all             | A character answers when it is addressed and stays quiet otherwise                           | [How a turn works](/api-docs/no-code-experiences/chat-experiences/running-the-room/how-a-turn-works.md)                                                      |
| There is no control that edits the brief    | The room type, the purpose, and the briefing are settled when the experience is created      | [Why the brief cannot be changed](/api-docs/no-code-experiences/chat-experiences/the-room-brief/why-the-brief-cannot-be-changed.md)                          |
| A finished conversation cannot be continued | Every opening of a chat experience starts a new room                                         | [Sessions and transcripts](/api-docs/no-code-experiences/chat-experiences/sessions-and-transcripts.md#why-every-opening-is-a-new-room)                       |
| A room link does not open for a colleague   | A chat experience and the rooms opened from it open only for the account that created them   | [The room will not connect](/api-docs/no-code-experiences/chat-experiences/troubleshooting/room-will-not-connect.md#the-room-does-not-open-for-someone-else) |

### The Chat Experiences controls are missing

If **My Experiences** shows neither a **Create a Chat Experience** button nor a **Chat experiences** section, contact <support@convai.com>.

{% content-ref url="/pages/vRkGq5EwreaG1y8CNs2j" %}
[What you need to use Chat Experiences](/api-docs/no-code-experiences/chat-experiences/prerequisites.md)
{% endcontent-ref %}

### Still blocked

When what you are seeing is on none of these pages, write to <support@convai.com> with the name of the experience, the room ID from the top bar, and the wording the room showed you.

If the room is working and you are checking whether what it did was meant to happen, the section overview sets out what a chat experience does and what it does not.

{% content-ref url="/pages/fr2HihLferHR6m3TZw7f" %}
[Chat Experiences](/api-docs/no-code-experiences/chat-experiences.md)
{% endcontent-ref %}


---

# 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://docs.convai.com/api-docs/no-code-experiences/chat-experiences/troubleshooting.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.