> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/pro/automation/insights.md).

# Insights (logs)

Insights in the Equipme Pro automation module: filter execution logs, check inputs and outputs per step, understand errors and set up error notifications.

**Path:** "Automation" → "Insights"

Under **"Insights"** you see what your flows have done: every message that flows from one component to the next is logged – with time, data and any error. This lets you check whether a flow runs as expected and find the cause when something goes wrong.

## Filtering logs

* **"Time range":** Choose a period – via quick selections ("Shortcuts") or with "From" and "To".
* **"Flows":** Select one or more flows; "Show selected" shows only the selected ones.
* **"Reload"** loads new entries, **"Load more"** older ones. With **"Start tracking"**, new entries are shown continuously; **"Pause tracking"** stops this.

You can also open the logs of **one** flow directly: in the [flow list](https://hub.equipme.io/pro/automation/workflows.md) via the **"Insights"** menu entry or in the flow designer via **"Logs"** in the toolbar. Logs are available for running and stopped flows.

## Reading an entry

Clicking an entry opens the details:

| Field                             | Meaning                                                                |
| --------------------------------- | ---------------------------------------------------------------------- |
| **"Status"**                      | "Success" or "Error"                                                   |
| **"Flow"**                        | The flow concerned                                                     |
| **"Source Component"**            | The component the data came from                                       |
| **"Target Component"**            | The component it went to                                               |
| **"Port Name"** / **"Port Type"** | Through which connection the data flowed; "In" = input, "Out" = output |
| **"Timestamp"**                   | Point in time                                                          |
| **"Message"** / **"Data"**        | The data passed – i.e. the input or output of the step                 |
| **"Error"** / **"Details"**       | Error message and details                                              |

**Tip:** Compare the data at the output of a step with what the next step expects. Most errors occur because a variable is empty or contains a different value than intended.

## Typical errors and solutions

| Symptom                                   | Cause and solution                                                                                                                                                                                     |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Flow does nothing, no entries             | The flow isn't started, or the trigger finds no matching data. Start the flow, check the trigger filters (e.g. "Customers", "After"). Some triggers only check at intervals – wait one or two minutes. |
| Error with "401" or "403", not authorized | Sign-in expired or permissions withdrawn. Test the account under [Accounts](https://hub.equipme.io/pro/automation/accounts.md) and reconnect it.                                                       |
| Error "404", not found                    | An ID doesn't match, e.g. a wrong variable or an entry that has already been deleted. Check the data of the previous step.                                                                             |
| Error "400" or "422", invalid data        | A required field is missing or has the wrong format, e.g. a date instead of an email address. Check field mapping and modifiers.                                                                       |
| Error "429", timeout or "5xx"             | The third-party system is overloaded or briefly unreachable. Automation retries such errors itself. Add a delay ("Delay") in loops.                                                                    |
| Flow was stopped                          | An account it used was removed, or the error handling stops the flow. Replace the account and restart the flow.                                                                                        |
| Duplicate records in the target system    | The flow processed the same transaction several times. Remember numbers already transferred in a [table](https://hub.equipme.io/pro/automation/files-and-tables.md) and check them first.              |

## Getting notified of errors

Automation does **not** send emails about errors by itself. For important flows, you build the notification yourself:

1. In the flow designer, open the critical step, e.g. "Create ERP order".
2. Set up an error output for this step via "Error handling".
3. Connect the error output with an email action ("Email" module) or a Teams message.
4. Put the flow name, the error message and the affected order number into the text as variables.

This way your team learns immediately if, for example, a customer order didn't arrive in the ERP. In addition, check "Insights" regularly with the filter set to your productive flows.

## Frequently asked questions

**Why don't I see any entries?**

Check the time range ("Time range") and the selected flows. If the flow hasn't processed anything since it was started, there are no entries yet.

**Do test runs also appear in the logs?**

Yes. Test runs are logged like normal executions.

**Do I see the logs of my customers' flows?**

No. Customers see the logs of their flows in their own portal.


---

# 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://hub.equipme.io/pro/automation/insights.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.
