> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user-documentation/bot-builder/check-errors-with-the-bot-flow.md).

# Check Errors With The Bot Flow

### How to Check Error Logs

#### Method 1: Inside Bot Builder

1. Go to **Bot Builder**.
2. Open the relevant **Bot Flow**.
3. Click on the **Error Log Icon**.
4. Review the details:
   * Step where error occurred
   * Node ID
   * Error description
5. Navigate to the mentioned step and fix the issue.
6. Save the flow.

**Example:**\
If the error says button title missing, go to that step and add the required button titles.

#### Method 2: From Bot Flow List

1. Go to the relevant **Bot Flow**.
2. Click the **Error Log Icon**.
3. View:
   * Date & Time
   * User number
   * Step ID
   * Error description
4. Click the **Step ID** to directly open the affected node.

**Note:** If the bot has stopped working or is not functioning properly, reviewing the error log is essential to identify and fix the issues.

{% embed url="<https://youtu.be/Z27dao63Syg>" %}


---

# 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://helpdocumentation.gitbook.io/user-documentation/bot-builder/check-errors-with-the-bot-flow.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.