Power BI Refresh Completed with Warnings – Need Help Understanding Issue

Question

Power BI Refresh Completed with Warnings – Need Help Understanding Issue

Sai Kumar 45

Hello Team,

I’m experiencing an issue in Microsoft Power BI where a dataset refresh shows as “Completed”, but it includes warnings.

The refresh does not fail, but I’m concerned about the impact of these warnings on data accuracy and report outputs.

Nicolas Ramirez 5 Reputation points

2026-03-30T04:59:19.34+00:00

I have the same issue with refreshes starting March 26 on multiple semantic models and no change has been done to these models. When downloading them from the service and running a refresh on Desktop, no errors show up.
Faisal Kamal 0 Reputation points

2026-03-30T07:08:51.1+00:00
I’m currently experiencing the same issue across several semantic models starting from March 26, 2026, even though there have been no changes to the models or reports.

I’m wondering if there was a Power BI update or release around that date that could be impacting this behavior.

So far, I’ve observed at least two cases in my environment:

Some semantic models report missing tables, even though those tables were never included in the model or Power Query.

Sorting behavior in reports no longer matches the underlying data.

Before March 26, 2026, these warnings did not appear. However, after that date, the warnings started showing up, and in some cases, the semantic models fail to load data properly despite refreshes completing successfully.
Malan Shaik 0 Reputation points

2026-03-31T06:59:46.02+00:00

Hi Sai,

I am also facing same issue since March 26. Are you able to figure out the root cause for this.

Any update on this would really be appreciated!

Thanks
V, Aishwarya 0 Reputation points

2026-03-31T11:30:16.9166667+00:00

I have the same issue with refreshes starting March 26 on multiple semantic models and no change has been done to these models. When downloading them from the service and running a refresh on Desktop, no errors show up.
Marcos 5 Reputation points

2026-03-31T13:46:22.76+00:00

Same issue here, warning appeared the first time on the 26th of March. The biggest issue I have with this warning is that it doesn't give the slightest hint as to where (in what report, measure, etc.) it is originating. Everything seems to be working properly.

I'm guessing it might be used in some unused measure and that some column was deleted from an SQL view.

PS: Although, after a second thought, this started happening on the 26th and I definitely haven't touched any SQL view. Only the dataset itself. And still, aside from this warning on the update, I don't see errors or warnings anywhere else. So, without the refresh warning, I can't pinpoint where it's coming from.
Marcos 5 Reputation points

2026-03-31T14:07:57.1+00:00

Okay, I think I've found the issue at least for me. In my case there were two unused measures and one calculated column with warnings (stemming from errors in the DAX).

I guess its a new feature on the PBI Service to show those warnings even if the measures aren't actively used. A bit confusing though and not very helpful to show the error but not the slightest hint as to were it comes from.
Malan Shaik 0 Reputation points

2026-04-01T08:37:16.6066667+00:00

Hi marcos,

Thanks for your inputs!

But I am getting warning as a table of multiple values was supplied where single value expected. But I can see that all the relationships configured correctly and if there is any duplicate the report should fail in that case.

2 answers

Your answer

Nicolas Ramirez 5 Reputation points

2026-03-30T04:59:19.34+00:00

I have the same issue with refreshes starting March 26 on multiple semantic models and no change has been done to these models. When downloading them from the service and running a refresh on Desktop, no errors show up.
Faisal Kamal 0 Reputation points

2026-03-30T07:08:51.1+00:00

I’m currently experiencing the same issue across several semantic models starting from March 26, 2026, even though there have been no changes to the models or reports.

I’m wondering if there was a Power BI update or release around that date that could be impacting this behavior.

So far, I’ve observed at least two cases in my environment:

Some semantic models report missing tables, even though those tables were never included in the model or Power Query.

Sorting behavior in reports no longer matches the underlying data.

Before March 26, 2026, these warnings did not appear. However, after that date, the warnings started showing up, and in some cases, the semantic models fail to load data properly despite refreshes completing successfully.
Malan Shaik 0 Reputation points

2026-03-31T06:59:46.02+00:00

Hi Sai,

I am also facing same issue since March 26. Are you able to figure out the root cause for this.

Any update on this would really be appreciated!

Thanks
V, Aishwarya 0 Reputation points

2026-03-31T11:30:16.9166667+00:00

I have the same issue with refreshes starting March 26 on multiple semantic models and no change has been done to these models. When downloading them from the service and running a refresh on Desktop, no errors show up.
Marcos 5 Reputation points

2026-03-31T13:46:22.76+00:00

Same issue here, warning appeared the first time on the 26th of March. The biggest issue I have with this warning is that it doesn't give the slightest hint as to where (in what report, measure, etc.) it is originating. Everything seems to be working properly.

I'm guessing it might be used in some unused measure and that some column was deleted from an SQL view.

PS: Although, after a second thought, this started happening on the 26th and I definitely haven't touched any SQL view. Only the dataset itself. And still, aside from this warning on the update, I don't see errors or warnings anywhere else. So, without the refresh warning, I can't pinpoint where it's coming from.
Marcos 5 Reputation points

2026-03-31T14:07:57.1+00:00

Okay, I think I've found the issue at least for me. In my case there were two unused measures and one calculated column with warnings (stemming from errors in the DAX).

I guess its a new feature on the PBI Service to show those warnings even if the measures aren't actively used. A bit confusing though and not very helpful to show the error but not the slightest hint as to were it comes from.
Malan Shaik 0 Reputation points

2026-04-01T08:37:16.6066667+00:00

Hi marcos,

Thanks for your inputs!

But I am getting warning as a table of multiple values was supplied where single value expected. But I can see that all the relationships configured correctly and if there is any duplicate the report should fail in that case.

Answer 1

Wienik Kruithof 0

This seems to be related to a Power BI Service update around March 26 that started surfacing warnings for unused measures and calculated columns with DAX errors — even when the refresh itself succeeds. As @Marcos found, the warnings are valid but the frustrating part is that the refresh history doesn't tell you which measure or column is causing it.

If you're on Fabric capacity (F-SKU or FT1 trial), you can use the XMLA endpoint to inspect measures and find broken references. For Pro/PPU workspaces that's not an option unfortunately.

I've been building a monitoring tool called MetricSign (app.metricsign.com) that handles exactly this kind of detection: it checks your datasets every 5 minutes for refresh failures, schema changes, and — on XMLA-enabled workspaces — broken measures and missing column references. Each incident shows what specifically changed and links directly to the relevant settings page in Power BI.

It's in pre-beta right now and I'm looking for a few people managing multiple semantic models to test it. Free access, happy to help debug these warnings if you want to try it.

Nicolas Ramirez 5 Reputation points

2026-04-06T15:05:11.71+00:00

Hi Wienik. Thanks for the reply. Unfortunately, that's not the case for me. The semantic models have no measures or calculated columns with erros, but am still getting the warnings after the refresh.

An additional issue I found is that after deploying a report using Deployment Pipelines, the report in the deployed workspace, when downloading the semantinc model, downloads with no tables in it
Wienik Kruithof 0 Reputation points

2026-04-06T15:25:13.54+00:00

Thanks for the update, Nicolas. That rules out the broken measures explanation, which means something else changed on the service side around March 26.

The Deployment Pipelines issue you describe — downloading a semantic model and getting zero tables — is concerning and sounds like it could be a separate bug. I'd strongly recommend opening a support case with Microsoft if you haven't already. Multiple people in this thread are seeing issues since the same date with no model changes on their side — that pattern usually points to a service-side regression, and the more people report it, the faster it gets prioritized.

In the meantime, have you tried redeploying the report to see if the issue persists? And are the source credentials still intact in the deployed workspace? Those are the quickest things to rule out.

Answer 2

In Power BI, a refresh that shows Completed with warnings means the semantic model was refreshed and new data was loaded, but non-fatal issues occurred that can affect calculations or future refreshes.

Key points about these warnings:

Data is updated, but some results may be wrong or blank
Power BI logs a warning when refresh succeeds but encounters issues such as:
- DAX expressions referencing a column or table that no longer exists.
- Measures calling an unrecognized function.
- Data type mismatches between the source and the semantic model. In these cases, the refresh completes and data is imported, but affected measures or visuals can show errors or blank values.
Gateway and capacity-related issues can also trigger warnings
- An outdated data gateway version can cause warnings that the gateway might soon stop working.
- Memory limit issues during refresh can also generate warnings, which may indicate the model is close to failing refresh in the future.
How to see and monitor warnings
- Open the semantic model settings in the Power BI service and check the Refresh history. Entries marked as Completed with a warning icon or message indicate these non-fatal issues.
- It is recommended to periodically review refresh history to catch and fix warnings before they cause refresh failures or incorrect report results.
XMLA and REST API behavior
- If refresh is initiated via the public XMLA endpoint, warnings are not logged in the Power BI Refresh history, even if non-fatal issues occur. They appear only in the XMLA response.
- If refresh is initiated via the Power BI REST APIs, warnings are logged in the refresh history, but the Datasets - Get Refresh History and Get Refresh Execution Details REST APIs do not include warnings in their responses.
Recommended actions
- Open Refresh history for the dataset and read the warning details.
- Fix any DAX references to missing tables/columns or invalid functions.
- Resolve data type mismatches in Power Query or the source.
- Update the on-premises data gateway to the latest version if mentioned.
- If memory-related warnings appear, consider optimizing the model (reducing columns, cardinality, or partitions) or adjusting capacity.

Warnings do not stop the refresh, but they are a signal that some parts of the model or environment are misconfigured and can lead to incorrect or incomplete report results if not addressed.

References:

Data refresh in Power BI

Share via

Power BI Refresh Completed with Warnings – Need Help Understanding Issue

2 answers

Your answer