> 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/falhas-de-atualizacao.md).

# Data Refresh Failures

How Power Monitor detects semantic model and Fabric item refresh failures, what the alert includes and how to reprocess refreshes.

Power Monitor automatically detects when a **semantic model refresh** or a **Fabric item run** fails, notifies the configured recipients and keeps the complete run history.

## What is monitored

| Type                                                                                 | How                                                       | Frequency        | Alert                                                 |
| ------------------------------------------------------------------------------------ | --------------------------------------------------------- | ---------------- | ----------------------------------------------------- |
| **Semantic models** on capacity (Premium, Fabric or Embedded)                        | Refresh history of all models in the monitored workspaces | Every 15 minutes | **Dataset Refresh Failed**                            |
| **Dataflows Gen2**, **data pipelines**, **notebooks** and **Copy jobs**              | Runs that end with a failure or cancellation              | Every 2 hours    | **Fabric Item Failed**                                |
| **Duration** of semantic models, Copy jobs, notebooks and dataflows (including Gen1) | Run much longer than the item's average                   | Every hour       | **Execution Duration Deviation** (optional, per item) |

{% hint style="info" %}

* Semantic model monitoring is turned on **once for the whole organization**, in **Settings › Monitoring**, and only generates alerts for failures that occur **after** it is turned on.
* Currently, Power Monitor does **not** monitor refresh failures of **paginated reports**, failures of **Dataflows Gen1** or models on **shared capacity (Pro)**, and does not detect runs stuck due to timeout.
  {% endhint %}

## What the alert includes

For a semantic model refresh failure:

* model and workspace name;
* time, status and who triggered the refresh;
* **error code and message**, translated when possible;
* technical identifiers of the run, useful for opening a ticket with Microsoft;
* links to the workspace and the model.

For a Fabric item failure: item, time, error code and message, and link.

## Where to track it

* **Monitoring › Semantic Models:** refresh history, failures and the **Retry Queue**, where an administrator selects failed refreshes to **reprocess**. Power Monitor triggers the new refreshes while respecting a maximum number of concurrent runs per organization. On a **Failed** row, hovering over the status shows the error and the model's recent history, and right-clicking offers **Investigate** (a technical dossier with an AI analysis).
* **Dashboards › Artifact Refreshes** and **Monitoring › Fabric Items:** runs of pipelines, notebooks, Copy jobs and Dataflows Gen2. In **Fabric Items**, hovering over the **Unhealthy** state shows the reason reported by Fabric, and right-clicking offers **Investigate**.
* **Performance › Average Execution Time:** average duration and deviations per item.
* **Monitoring › Data Freshness:** confirms whether the data in important tables is actually up to date, even when the refresh "succeeded".
* **Governance › Operations › Schedules:** heat map and timeline of schedules, to find congested time slots.

## Why does a refresh fail?

The most common causes are:

* **Expired credentials** for the data source;
* **Gateway offline** (see [Gateway Monitoring](/en/principais-funcionalidades/monitoramento-de-gateways.md));
* **Unreachable data source** (server, file or API unavailable);
* **Overloaded capacity**, without resources to process the refresh (see [Capacity Monitoring](/en/principais-funcionalidades/monitoramento-de-capacidades.md));
* Refresh **timeout** exceeded;
* **DAX or Power Query (M) error** that prevents processing.

{% hint style="info" %}
Power Tuning offers [Managed Monitoring](/en/managed-monitoring/monitoramento-gerenciado.md), where our team handles these failures for you.
{% endhint %}

## Related pages

* [Semantic Models (Monitoring)](/en/power-monitor/monitoramento/modelos-semanticos.md)
* [Artifact Refreshes](/en/power-monitor/dashboards/atualizacoes-de-artefatos.md)
* [Average Execution Time](/en/power-monitor/performance/tempo-medio-de-execucao.md)
* [Real-time alerts](/en/principais-funcionalidades/alertas-em-tempo-real.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/falhas-de-atualizacao.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.