Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

The Fabric community is upgrading! Read all of the details including the timeline and what you can expect. Learn more

Reply
FPE
New Member

Automatic Refresh Failure with Internal Service Error

Hello everyone,

 

I'm facing an issue with my Power BI report that has been puzzling me. Whenever I update the file manually, there are no problems, and I can easily publish it. However, when I schedule automatic refreshes, I consistently encounter the same error:

 

"Failure details: The last refresh attempt failed because of an internal service error. This is usually a transient issue. If you try again later and still see this message, contact support.

<ccon>Expression.Error: We cannot convert the value <ccon>"[List]"</ccon> to type <ccon>Table</ccon>.. </ccon>. The exception was raised by the IDataReader interface. Please review the error message and provider documentation for further information and corrective action. Table: Parceiros TOTAL."

 

Despite my efforts, I haven't been able to identify the issue. Has anyone else encountered a similar problem or has insights into what might be causing the error during automatic refreshes? I would be extremely grateful for any suggestions or solutions to resolve this matter.

Thank you all in advance for your time and assistance!

2 REPLIES 2
ibarrau
Super User
Super User

Hi. Types can be tricky. You should refresh the whole report at the original file .pbix. Check if it fails to deep dive on the error. If it refreshes completely it might show warning of errors, go and filter by error those tables because there is one that can pass the desktop refresh but won't the Service one.

I hope that helps,


If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Happy to help!

LaDataWeb Blog

Thanks so much for the feedback.
That's precisely what happens. An automatic update always gives the error, but manually, by Power BI Desktop, it works like a charm.
After manually updating, I get three queries with the danger signal. When I open them, there is no other indication, the danger sign disappears, and everything is OK!
The situation is driving me crazy, and I believe that the solution is something straightforward and that I'm missing it.

Helpful resources

Announcements
FabCon and SQLCon Barcelona 2026

FabCon & SQLCon – Barcelona 2026

Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.