> For the complete documentation index, see [llms.txt](https://docs.hablla.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hablla.com/hablla-docs-en/reports/hablla-reports-and-logs/flow-executions.md).

# Flow executions

Flow execution consumption report

#### Flow Executions – Overall Total

The report of **Flow Executions** provides a consolidated view of the performance of automated flows within the Hablla ecosystem. It classifies executions by status, allowing assessment of the operational health of automations.

With this dashboard, you can:

* Identify the number of flows **successfully completed**, ensuring that automations are delivering real value.
* Monitor executions **in progress**, tracking flows that are still active at the time of analysis.
* Detect flows that **failed** or were **canceled**, allowing identification of bottlenecks, configuration errors, or points for improvement.
* Track the **success vs failure ratio** in real time, ensuring greater governance over automated journeys.
* Export reports in **PDF** or **CSV** for more detailed analyses and follow-up with technical teams.

This report is essential for operations leaders and automation teams, as it offers a clear view of **the efficiency and reliability of flows**, supporting decisions for continuous improvement and scalability.

<figure><img src="https://1592162275-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrmxWrIrMauHcIrsuqfGq%2Fuploads%2FZWOlL82UN2A2oOgx6Lyf%2Fimage.png?alt=media&amp;token=9fa7ac2b-28be-41e8-a352-9cbb77b2bcd9" alt=""><figcaption></figcaption></figure>

#### Flow Executions – Monthly Consumption (last year)

The report of **Monthly Consumption of Flow Executions** allows tracking the evolution of automations performed over time, offering a historical view of flow performance.

With this dashboard, you can:

* Analyze the **monthly number of executions** of flows, segmented by status (**completed, running, failed or canceled**).
* View trends of growth or decline in the use of automations over the months.
* Identify **execution peaks**, correlating them with campaigns, seasonal actions, or operational changes.
* Measure the **operational efficiency** of automations, tracking the success rate compared to failures.
* Export the data in **PDF** or **CSV** for managerial reports or external analyses.

This report is essential to assess the **maturity and scalability of automations**, helping managers and analysts make strategic decisions about adjustments, expansion, or reconfiguration of flows according to usage history.

<figure><img src="https://1592162275-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrmxWrIrMauHcIrsuqfGq%2Fuploads%2FnZUkOXaoGakOS3jWbD1y%2Fimage.png?alt=media&amp;token=45e6b581-e5fd-478a-9da3-b3d8d518da60" alt=""><figcaption></figcaption></figure>


---

# 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://docs.hablla.com/hablla-docs-en/reports/hablla-reports-and-logs/flow-executions.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.
