The **Flow Report** is a structured PDF file automatically generated after a **successful scheduled run**. It walks you through exactly what was executed, which is great for documentation, compliance, or audits.

In this article, you’ll learn about the different sections included in the report:

- [Header Information](https://docs.leapwork.com/com/leapwork/www/index.html)
- [Keyframes Section](https://docs.leapwork.com/com/leapwork/www/index.html)
- [Report naming and storage](https://docs.leapwork.com/com/leapwork/www/index.html)

## Header Information

The first page acts as a **summary sheet** for the test run.

It includes:

- **Team name**  
- **Flow name**  
- **Description**  
- **Flow version**  
- **Flow state at execution time**  
- **Leapwork flow ID**  
- **A link to open the flow directly in Leapwork Flow**  
  
  _(Requires proper setup in Adobe Acrobat)_  
- **Start and end timestamps** of the run  
- **Total run time**  
- **Execution Agent/Host** used  
- **Execution result** (Passed / Failed)  
- **Schedule details:**  
  - Schedule name and ID  
  - Run ID  
  - Run list name  
  - Whether the schedule was frozen  
  - Whether only published flows were allowed

This page gives you all the **contextual metadata** about the run in a clean, digestible format.

## Keyframes Section

Starting from page 2, the Flow Report displays a sequence of keyframes,each one representing the execution of a specific building block in the flow.

Every keyframe includes the following elements:

- **Keyframe number and execution timestamp:** This shows when this block was processed within the flow run.

_Example: Keyframe 13 – Executed at 25-06-2025 10:16:22 +00:00_

- **Block start time / end time / elapsed duration:** Indicates when the block began and finished, and how much time had passed since the run started.

_Example: Block start time/End time, Elapsed: 10:17:03/10:17:05 +00:00, Elapsed: 00:00:42.8433100_

- **Building block used:** The type of block executed, such as _MobileElementAction_, _ClickWebElement_, etc.

- **Building block name:** The custom or default name of the block, e.g., _Mobile Action_.

- **System log message:** A line describing the system's log output during that step. This matches what is shown in the Flow’s Action Log.

_Example: Action Swipe was executed on mobile element: Position ({X=0,Y=435})_

If a **screenshot block** is used (e.g., _Log Mobile Screenshot_, _Log Web Screenshot_), the report will also display:

- The captured image  
- The timestamp  
- All relevant metadata and messages

This structure allows teams to **reconstruct and verify the execution path**, making it highly valuable for traceability and compliance reporting.

## Report Naming and Storage

Reports are stored **locally in Flow**, pulled from the **Controller** after run completion. You can access them via:

`C:\Users\<your-username>\AppData\Local\Temp\LEAPWORK\Studio`

**Folder structure:**  
`<TeamName>_<RunListName>_<ScheduleName>_<Timestamp>`

**PDF filename structure:**  
`<FlowName>_<Environment>_<Timestamp>.pdf`

The folder may contain multiple PDF reports if the schedule includes multiple flows.

**Note:** Flow Reports are subject to Flow’s **retention policy**. If Flow is restarted or retention rules apply, locally stored reports may be removed.

You can always retrieve them again by right clicking the schedule and selecting **Open PDF report folder**.