> 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/4.-embed-for-end-user/4.2-embed-end-user-logs.md).

# 4.2 Embed End User Logs

## Overview

1. Users can click on the details icon of any enabled integration (Flow) to see an overview of all runs:<br>

   <figure><img src="/files/GCWgxbnfNYC4v6IUm7z4" alt=""><figcaption></figcaption></figure>
2. From there users can look at details of specific Flow Runs, to see number of successful and unsuccessful records per entity:

   <figure><img src="/files/lwHPEGqdr9H8ixsce3do" alt=""><figcaption></figcaption></figure>
3. Users can drill down even more by looking at the error details of the unsuccessful records to see why there has been an error and thus potentially adjust their data in order to prevent the error in the next run:

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

## Terms/Wording

To make the end user logs useful to a wide variety of use cases, general terms/wordings are used.

| Term      | Description                                     | Examples                              |
| --------- | ----------------------------------------------- | ------------------------------------- |
| Record    | Collection of related fields treated as a unit  | Row, one data entry                   |
| Entity    | The type of record                              | Contact, company, ticket, building, … |
| Record ID | Unique identifier of a record (end user facing) | Company id, ticket number, …          |
| Run       | Flow Run                                        |                                       |

E.g. if 5 companies are synced between two systems, there would be 5 records of the entity company. If one of them failed, its ID (company ID) would be the Record ID.


---

# 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/4.-embed-for-end-user/4.2-embed-end-user-logs.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.