Forum Discussion
Warning Observed in Power BI Service Refresh History - Refresh completed with warnings
Post March, it has been observed that all production‑published Power BI reports are refreshing with the warning message “Refresh completed with warnings.” There are no errors in the reports, and the report front end is functioning as expected with no visible issues.
Has anyone encountered this before or been able to fix it? Any advice or guidance would be highly appreciated.
Hi 321shekhar,
This issue usually happens due to non-fatal semantic model or DAX validation warnings that occur during the Query Cache phase after a dataset refresh completes successfully. According to Microsoft documentation, refreshes can finish with warnings if DAX expressions or model objects reference invalid or renamed columns or tables, though reports may still work as expected.
Query caching in Power BI Premium - Power BI | Microsoft Learn
Data refresh in Power BI - Power BI | Microsoft Learn
Dataset Refresh History Enhancements - Microsoft Fabric CommunityThank you.
8 Replies
Hi 321shekhar ,
This warning messages are now appearing when you have some semantic model problems that do not impact your refresh, like a incorrect login, but have impact on the overall result of the semantic model.
In my case I have a warning about a sort by column that is breaking the rules for the sort by.
It seems like there are a couple of problems in your semantic model that there are some missing columns (Report Date) and that the 2 measures (Total Budget (AUD) YTD, Selected Measure 1) have issues or don't exist in your model but are being referenced in other measures.
My suggestion is for you to do a revision on your semantic model for this 3 values.
Post March, it has been observed that all production‑published Power BI reports are refreshing with the warning message “Refresh completed with warnings.” There are no errors in the reports, and the report front end is functioning as expected with no visible issues.
Has anyone encountered this before or been able to fix it? Any advice or guidance would be highly appreciated.
Hi 321shekhar ,
This usually could be from below:
Schema drift – where a column or datatype changes upstream and Power BI Service just adjusts quietly
Query folding breaking – with M logic, one step fails folding and the rest runs locally, which triggers this
Source inconsistencies – APIs or incremental loads sometimes return slightly uneven data (especially with late-arriving records)
Gateway issues – intermittent retries, some connectivity glitchesWhat we can possible check to avoid this:
Open in Power BI Desktop and validate query folding
Double-check if anything changed upstream (schema/datatype)
If incremental refresh is there, just make sure partitions are behaving as expectedHope this helps.
Thanks,
Pallavi
Hi 321shekhar,
Have you had a chance to review the solution we shared by pallavi_r? If the issue persists, feel free to reply so we can help further.
Thank you.
Hi 321shekhar,
Checking in to see if your issue has been resolved. let us know if you still need any assistance.
Thank you.
Issue still continues - not resolved. I am still looking for help. Thanks
Hi 321shekhar,
This issue usually happens due to non-fatal semantic model or DAX validation warnings that occur during the Query Cache phase after a dataset refresh completes successfully. According to Microsoft documentation, refreshes can finish with warnings if DAX expressions or model objects reference invalid or renamed columns or tables, though reports may still work as expected.
Query caching in Power BI Premium - Power BI | Microsoft Learn
Data refresh in Power BI - Power BI | Microsoft Learn
Dataset Refresh History Enhancements - Microsoft Fabric CommunityThank you.
