Forum Discussion
Errors reported but no errors found
- 1 year ago
Hi IanDavies,
Thanks for sharing the details. Also thanks to danextian, ajaybabuinturi, rohit1991, for those inputs on this thread.
It sounds like you're running into a confusing issue you are getting error messages during refresh, but when you go into Power Query, everything looks fine and the data is loading as expected. I can see how that would be frustrating, especially after moving the report to SharePoint.From what you have described, this may be caused by errors that happen temporarily during refresh, but Power BI still flags them even if the data ends up loading properly. This can happen with:
- Queries that merge or join data where some rows do not match,
- Steps that silently remove errors (like "Removed Errors"),
- Or even small connection hiccups when accessing files on SharePoint.
Here are a few things you can try to resolve the issue:
- In Power Query, check each of the queries with a warning message and expand the Applied Steps panel on the right.
- If you see a step called "Removed Errors", try deleting it just temporarily sometimes this step hides the real error rows from view.
- If you’re doing any merge/join steps, double-check that the keys used to match the data aren’t missing or mismatched.
- You can also use a Power Query trick to catch any errors without stopping the refresh. This tells Power BI to continue even if something goes wrong in a specific row.
- If everything still works and the visuals look good, the warning might just be cosmetic. You can enable Diagnostics tracing (under File > Options > Diagnostics) to dig deeper, but it’s optional.
Kindly refer to the below mentioned documentation links for better understanding:
M Language Error Handling - Power Query M | Microsoft LearnLet me know what you find after giving these steps a try happy to help you investigate this further.
Thank you for using the Microsoft Community Forum.
Hi IanDavies
This is a common issue after moving files to SharePoint — Power BI may still carry over old error-handling logic even if errors no longer exist.
Here's what's likely happening:
-
Your query probably includes a step like “Kept Errors” or an applied transformation that previously captured errors (e.g., missing files).
-
After the SharePoint switch, these errors no longer exist, but Power BI still triggers the "view errors" warning during refresh.
What you can do:
-
Go to Power Query, and look for any step named “Kept Errors” or similar.
-
If that step returns an empty table, it's safe to delete it — along with any related custom error steps immediately after.
-
Then refresh again. If there are no actual errors now, the warnings should stop appearing.
This should clean up any false error triggers left over from earlier file structure or schema changes.