> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jelou.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Observability - Executions Report
> Download the detail of your workflow executions as a spreadsheet, honoring whatever filters you have applied
From **Logs** you can download the detail of your workflow executions as a spreadsheet. What you get is exactly what you see on screen: the report honors the date range and every active filter, it is not a full dump.
Use it to keep a record of what you are billed for, or to review a set of executions offline without opening them one by one.
## How to download it
Go to the **Logs** section of your project and pick the **Workflows** or **Tools** tab, depending on what you want to export.
Set the date range and any filters you need: channel, status, workflow, user. The file will contain exactly that set.
You will find it on the right of the filter bar. Generation is asynchronous: the request is dispatched and the file shows up in the **Downloads Center** once it is ready.
You do not have to stay on the screen waiting. Keep working and come back to the Downloads Center later.
If your filters return no results, the system tells you there is no data instead of handing you an empty file.
## Columns in the file
| Column | What it holds |
| --------------------- | ----------------------------------------------------------- |
| `Execution ID` | Unique identifier of the execution |
| `Parent execution ID` | The execution that invoked it, when it is a child execution |
| `Root execution ID` | The execution that started the whole chain |
| `Level` | `Parent` or `Child` |
| `User name` | Name of the user who originated the execution |
| `User ID` | Identifier of the user |
| `Workflow` | Name of the workflow that ran |
| `Project` | Project it belongs to, when applicable |
| `Channel` | Channel the conversation came in through |
| `Status` | Outcome of the execution |
| `Origin` | What triggered it |
| `Start date` | When it started |
| `End date` | When it finished, empty when the execution never did |
Headers come in your configured language: Spanish, English or Portuguese.
## Parent-child hierarchy
When one workflow invokes another, three columns work together to let you tell who called whom.
`Level` tells you at a glance whether the row is a **parent** execution — it started on its own — or a **child**, invoked from another one. `Parent execution ID` tells you which one invoked it, and `Root execution ID` takes you to the origin of the whole chain, however many levels of nesting there are.
The three columns can come back empty when hierarchy information is not available for that execution. The report leaves the cell blank rather than assuming a value.
## Dates and time zone
Dates in the file are expressed in the **time zone configured in your profile**, not in the server's UTC. If you have none configured, your browser's zone is used.
The format is `YYYY-MM-DD HH:MM:SS` on a 24-hour clock. That order is deliberate: in a spreadsheet it sorts correctly alphabetically and Excel recognizes it as a date.
The file's time zone and the filter's date range are two different things. The filter decides **which executions are included**; the time zone decides **how their dates are displayed**.
## Size limit
The report supports up to **1,000,000 rows**. If your filters return more, the download is rejected with the message *"Error generating report download, exceeds resource limits"* and no file is produced.
If you hit that limit, narrow the date range or add a workflow or channel filter.
Below that ceiling the file is assembled for you. If the set is large it is split into several files, and you will find all of them in the Downloads Center.
## Use cases
An account that needs to justify its invoice to finance: it downloads the detail for the full period and keeps it as backing evidence for the summary it receives.
A team that saw many failed executions yesterday: it filters by status and channel, downloads the set and reviews the identifiers without opening each execution in the interface.
A workflow that invokes two others, and one of them fails: `Root execution ID` groups every row of the same chain, and `Level` separates the parent from the children.
## Related articles
What counts as an execution and how it affects your billing
Configure tracking events to feed your metrics