High severityrefresh
Power BI Refresh Error:
Dataflow refresh completes quickly without updating data
What does this error mean?
A dataflow refresh completes in an unusually short time with no errors reported, but the underlying data has not actually changed. This is a silent failure pattern that can go undetected without active monitoring.
Common causes
- 1Incremental refresh detected no new data beyond the already-processed watermark, so no rows were loaded
- 2The dataflow is connected to a cached or previously materialized source that has not been updated upstream
- 3A filter or query fold condition is silently excluding all rows, resulting in an empty but technically successful load
- 4The dataflow entity is configured with a stale or incorrect date/time parameter that causes the incremental window to return zero records
How to fix it
- 1Step 1: Check the row count and last-modified timestamp on the dataflow entity in the Power BI service after the refresh to confirm whether data actually changed.
- 2Step 2: If using incremental refresh, verify that the incremental refresh policy watermark is set correctly and that new data exists beyond the current watermark boundary.
- 3Step 3: Review any filter conditions or query parameters applied to the dataflow query — check that date range parameters are dynamic and not hardcoded to a stale value.
- 4Step 4: Temporarily disable incremental refresh and perform a full refresh to confirm whether the underlying source contains the expected data.
- 5Step 5: Enable dataflow refresh history and duration logging in MetricSign to alert when a refresh completes significantly faster than the historical baseline, which signals a silent no-op refresh.