> 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/dokumentation/automation/insights.md).

# Insights (logs)

Insights in the automation module: filter execution logs, view a step's inputs and outputs, understand errors and set up notifications.

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

**Insights** shows what your flows have done: every step a message takes from one component to the next is logged – with time, data and, if applicable, an error message. This is where you find out whether a flow ran and why something did not work.

## Filtering logs

* **"Time range"** – the period, e.g. the last 24 hours or a fixed range with "From" and "To".
* **"Flows"** – select one or more flows ("Select flows"). Without a selection, you see all flows of the workspace.

At the top, a bar chart shows how many entries occurred in which period – so peaks and gaps stand out. Below are the individual entries; "Load more" loads older ones.

* **"Start tracking"** shows new entries live, **"Pause tracking"** freezes the view.
* **"Reload"** reloads the list.

You can also reach the logs of a single flow via **"Insights"** in the flow's menu in the [flow list](https://hub.equipme.io/dokumentation/automation/workflows.md) or via **"Logs"** in the [flow designer](https://hub.equipme.io/dokumentation/automation/flow-designer.md). 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 the entry belongs to                                                     |
| "Source Component"        | The component the data came from                                                  |
| "Target Component"        | The component that received the data                                              |
| "Port Name" / "Port Type" | The input ("In") or output ("Out") the data passed through, e.g. "true" or "item" |
| "Timestamp"               | Time                                                                              |
| "Message" / "Data"        | The complete data of this step – what the component received or returned          |
| "Input messages"          | The component's input data                                                        |
| "Error" / "Details"       | For errors: error message and technical details                                   |

This lets you check step by step which values actually arrived – for example whether the email address was empty or a date came in a different format than expected.

## Reading error messages

1. Look for status "Error" and open the entry.
2. **"Target Component"** shows which step failed.
3. **"Error"** gives the cause, often with a status code from the system called.
4. Check in **"Message"** or **"Input messages"** which data the step was called with.
5. Fix the component in the designer and test again with test data.

## Typical errors and solutions

| Symptom                                                             | Cause                                                                                 | Solution                                                                                                                                     |
| ------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| No entries, flow does nothing                                       | Flow not started or trigger never fired                                               | Start the flow ("Running"); check the trigger settings (correct account, schedule, filter)                                                   |
| Scheduler runs at the wrong time                                    | Time zone not set                                                                     | Set the time zone in the Scheduler                                                                                                           |
| Error with 401 or 403                                               | Access invalid or permission missing (key deleted, password changed, right withdrawn) | Test the account under [Accounts](https://hub.equipme.io/dokumentation/automation/accounts.md), reconnect, check permissions at the provider |
| Error with 400 or 422, or a note about invalid input                | Wrong or empty value in a field, e.g. a date instead of an email address              | Check the variable mapping in the inspector; use a modifier if needed                                                                        |
| Error with 404                                                      | The record does not exist (anymore)                                                   | Check the ID mapping; catch the case with a filter or condition                                                                              |
| Error with 429, 5xx or a timeout                                    | System overloaded or unreachable                                                      | Retried automatically; for large lists, set a "Delay" in the loop                                                                            |
| Flow suddenly stopped                                               | An account it used was removed, or a component's error handling stops the flow        | Select the account again, fix the error, start the flow again                                                                                |
| Loop returns incomplete results                                     | Entries were filtered out or failed; parallel processing                              | Set Each to "Sequential"; check failed entries in Insights                                                                                   |
| Message about reached limits (number of flows, components, storage) | Limit reached for your company                                                        | Remove flows, files or table entries you no longer need; contact your provider or account manager if necessary                               |

Errors in the equipme connector and the other connectors are covered in the "Troubleshooting" sections on the [connector pages](https://hub.equipme.io/dokumentation/automation/connectors.md).

## Getting notified of errors

The automation module does not send error emails on its own. Errors always appear in Insights – to make sure you do not miss them, build the notification into the flow:

* **Use the error output:** in the error handling of an important component, enable the error output (where offered) and connect it to an email component, e.g. **Email › Send Email** to IT. Insert the error message into the text with a variable.
* **Error trigger:** if the designer offers a trigger for logged errors (e.g. "OnError"), use it to build a separate monitoring flow that sends an email or Teams message for every error. The monitoring flow must be started.
* **Business check:** for critical processes, additionally send a success notice at the end, e.g. a daily summary. If it does not arrive, something is wrong.

## Frequently asked questions

**Do I have to stop a flow to see its logs?**

No. Logs are available for running and stopped flows.

**Why does a test run show up in the logs?**

Tests really execute the flow and are therefore logged as well.

**A step failed but was later executed successfully.**

The automation module retries temporary errors (e.g. timeouts) automatically. The first attempt then shows as "Error" and the later one as "Success" in the logs.

**How long are logs kept?**

Logs are not kept indefinitely. If you need results permanently, store them in the flow, e.g. in a [table](https://hub.equipme.io/dokumentation/automation/files-and-tables.md#tables) or as a file.


---

# 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/dokumentation/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.
