> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user/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/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 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://helpdocumentation.gitbook.io/user/bot-builder/check-errors-with-the-bot-flow.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.