> For the complete documentation index, see [llms.txt](https://docs.powermonitor.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.powermonitor.com.br/en/principais-funcionalidades/monitoramento-de-dataflows.md).

# Dataflow Monitoring

What Power Monitor tracks in Power BI and Microsoft Fabric Dataflows Gen1 and Gen2.

Power Monitor inventories the **dataflows** in your tenant and tracks their runs, with different handling for Gen1 and Gen2.

## Dataflows Gen1 vs. Gen2

| Aspect                                        | Dataflow Gen1                                 | Dataflow Gen2                                        |
| --------------------------------------------- | --------------------------------------------- | ---------------------------------------------------- |
| **Where it is created**                       | Power BI                                      | Microsoft Fabric                                     |
| **Data destination**                          | Dataflow storage (or Azure Data Lake Storage) | OneLake, Lakehouse, Warehouse and other destinations |
| **Failure alert**                             | ❌ No                                          | ✅ **Fabric Item Failed**                             |
| **Duration and execution duration deviation** | ✅ Yes                                         | ✅ Yes                                                |
| **Inventory, lineage and connections**        | ✅ Yes                                         | ✅ Yes                                                |

## What is monitored

* **Dataflows Gen2:** runs are collected **every 2 hours**; a run that ends with a failure or is cancelled generates the **Fabric Item Failed** alert.
* **Dataflows Gen1:** run duration is collected **every 2 hours** and feeds the **Average Execution Time** screen and the **Execution Duration Deviation** alert (optional, per item).

{% hint style="info" %}
Currently, Power Monitor does not generate failure alerts for Dataflows Gen1 and does not detect dataflows stuck in execution.
{% endhint %}

## Where to track it

* **Monitoring › Fabric Items** and **Dashboards › Artifact Refreshes:** Dataflows Gen2 runs.
* **Performance › Average Execution Time:** duration and deviations (Gen1 and Gen2).
* **Governance › Data and Engineering › Data Engineering:** dataflow inventory.
* **Data Quality › Data Lineage:** where the dataflow reads from and who consumes its data.

## Common causes of dataflow failures

* **Expired credentials** for the data source;
* **Unreachable data source**;
* **Gateway offline**, for on-premises sources;
* **Overloaded capacity**;
* **Error in the Power Query (M) transformation**;
* **Destination unavailable** or with an incompatible schema.

## Related pages

* [Data Refresh Failures](/en/principais-funcionalidades/falhas-de-atualizacao.md)
* [Average Execution Time](/en/power-monitor/performance/tempo-medio-de-execucao.md)
* [Data Lineage](/en/power-monitor/qualidade-de-dados/linhagem-de-dados.md)


---

# 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.powermonitor.com.br/en/principais-funcionalidades/monitoramento-de-dataflows.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.