> For the complete documentation index, see [llms.txt](https://docs.locoia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.locoia.com/embed-white-label-portal/embed-admin-setup/flow-building/error-handling.md).

# 1.3 Embed Error Handling

### Error notifications

You can set up [error notifications](/automation/flow-builder/flow-run-data-retention-and-logging.md#error-notifications) in the flow you built for embed to be notified of all errors that happen in the flows of your users.

### Finding errored flows

Under the submenu Embed, you have an overview of all Integrations enabled by the end users for all Embed configurations you have.

<figure><img src="/files/ZHOyCJetuPPFvuhiU0Oq" alt=""><figcaption></figcaption></figure>

To find a particular Integration of a specific end user we provide you with powerful searching and filtering capabilities. You can search by:

* Integration name
* Embed Flow name
* User ID
* Account ID

You can filter by:

* Embed Flow name
* Configuration name
* Group name

To make searching easier, all Integrations are named based on the following schema:

`Embedded flow - {{ embed_group_name }} - {{ flow_name }} - {{ embed_account_name }} ({{ embed_account_id }}) - {{ embed_user_name }} ({{ embed_user_id }})`&#x20;

and have the following tags:

* Embedded
* `{{ embed_group_name }}`
* `{{ embed_account_name }}`
* `{{ embed_account_id }}`

### Handling embed flow errors

You can handle flow errors in embed flows, just like for normal flows as [explained here in custom error handling](/automation/flow-builder/custom-error-handling.md).

### Logging embed flow errors

You can log flow errors in embed flows, just like for normal flows as [explained here in custom error logging](/automation/flow-builder/error-handling-flows.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://docs.locoia.com/embed-white-label-portal/embed-admin-setup/flow-building/error-handling.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.