---
title: Logs
slug: blueprint/logs
docTags: kEeQ6vT7FPx-7PjzNcWzO
createdAt: 2026-04-17T18:28:52.012Z
---

:::CtaButton{label="🔵 ALC" openInNewTab="false"}

:::

The Logs tab provides a trace log experience for developers actively working in PAD flows. Rather than writing messages to a text file throughout execution, developers can use PAD's native **Log Message** action and review all output here in a structured, filterable table.

***

# Setup

Logs requires two settings to be enabled in **Settings -> RPA Management -> Analyze -> Power Automate Desktop**:

- **Enable PAD Log** — turns on log capture for this instance
- **Dataverse Synchronization** — must be configured (located just below the log enable setting)

***

# Import 

Log data is imported with the flow. In the import wizard, use the Import Flow Activity History dropdown to select how far back to pull historical log data.

***

# Reading the Log Table

Each row represents a single Log Message action output from a flow run. The run is identified by its date and time.

- **Subflow** — the subflow in which the Log Message action was executed
- **Action Index** — position of the Log Message action within the subflow
- **Message** — the message string output by the Log Message action
- **Variable Name** — if the message was sourced from a variable, the variable name is shown here
- **Log Level** — Info, Warning, or Error — as specified in the Log Message action

The table filter allows filtering across any combination of columns.