---
title: "Execution logs"
slug: "flows-execution-logs"
updated: 2026-07-14T08:49:09Z
published: 2026-07-14T08:49:09Z
canonical: "docs.connect.visma.com/flows-execution-logs"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.connect.visma.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Execution logs

#### **What is an execution log?**

Every time one of your flows runs, Flows records it as an execution. Think of it as a history entry that answers three simple questions for each run:

- When did it run?
- What information did it receive and process?
- Did it work or did something go wrong?

The list of all these runs is what we call the execution logs.

#### **How to open the execution logs**

1. Open the flow you want to look at.
2. In the left-hand menu of the flow, click Workflow executions. A panel titled Executions slides in from the side.

![](https://cdn.document360.io/0ec30182-e256-4eca-ab6a-d067d83d0895/Images/Documentation/Flows_ExecutionHistory.png)

**Note**: the flow must be published for this option to work. If the menu item is greyed out, hovering over it shows the message "Publish the Flow to view executions."

#### **Searching the logs**

At the top of the panel there's a search box labelled "Search by input data or error message". Type something that would appear in the message the flow received — for example a company/organization number, a customer number, or an invoice number — and the logs will be filtered to runs that contain it.

**Tips to search effectively:**

- Search looks inside the data the flow received (the incoming message) and any error message — so search for values that actually appear in the message itself, not internal names.
- If you type several words, a run must contain all of them to appear. So start with one strong, unique value (like an organization number) and add more words only if you need to narrow things down.
- Use the Clear button next to the box to empty the search.

#### **Filtering the logs**

Click **Show** filters to open more options. The available filters are:

- **Date** — pick a date range to only see runs within those days.
- **Show executions by** — choose whether the date range applies to the **Received Date** (when the message arrived) or the **Executed Date** (when the flow actually ran it).
- **From / To** — narrow the range down to a specific time of day.
- **Status** — show only certain outcomes: **All statuses**, **Succeeded**, **Failed**, or **In progress**.
- **Step** — show only runs that involved a particular step of the flow.

When you've set your filters, click **Search**. To start over, click **Reset filter.**

#### **Reading the results**

After searching, you get a list of runs, with a count at the top (*e.g. "Fetched 12 executions"*). If there are many results, use the page arrows at the top to move between pages.

Each run in the list shows:

- **Start** — the date and time it began.
- **End** — the date and time it finished (shown as a dash if it's still running).
- A **status label**: Success, In progress, Received, Cancelled, or Failed.
- The **flow version** that ran.

![](https://cdn.document360.io/0ec30182-e256-4eca-ab6a-d067d83d0895/Images/Documentation/Flows_Executions.png)

#### **Looking into a failed run**

If a run failed, you can expand it (using the arrow button on the row) to see more. It shows a message "There was an error with this execution", which step failed, and the error message describing what went wrong.

![](https://cdn.document360.io/0ec30182-e256-4eca-ab6a-d067d83d0895/Images/Documentation/Flows_FailedExecution.png)

#### **Good to know**

How long logs are kept: execution logs are stored for 180 days. Anything older than that will no longer appear.

What the logs do and don't tell you: the logs show what the flow received and what it did with it. They don't record who in another system requested an action or why — for that kind of question you need the audit trail of that other system.