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

Join us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.

Reply
BladeLyfe
New Member

Dataset Refresh Error ValidateMarkupTags IDbCommand interface

Hello world, 

 

I have been having an issue with report refresh failures in the service and I cannot trace the root cause or solve. Here is the error I am getting: 

 

 

 

[ValidateMarkupTags]<ccon>[ccon]DataSource.Error: [ccon]Web.Contents failed to get contents from 'https://api.redacted/1' (503): Service Temporarily Unavailable[/ccon]. DataSourceKind = [ccon]Web[/ccon]. DataSourcePath = [ccon]https://api.redacted/1[/ccon ]. Url = [ccon]https://api.redacted/1[/ccon ]. [/ccon]. The exception was raised by the IDbCommand interface.</ccon> Table: Table1.

 

 

 

I have been getting this error across many downstream queries where I am merging data, even if the query that is throwing this error doesn't hit the API endpoint itself. 

 

The only thing I can think of to try that I have not yet is to implement table.buffer for the root API calls, but I don't know. 

This is only an issue in the service, and it has never failed in desktop refresh. I would say of my 8 daily refreshes, about 3 are failing each day due to this issue. 

 

Help me PBI community, you're my only hope!

1 ACCEPTED SOLUTION
BladeLyfe
New Member

So there is essentially no way to prevent power bi from hitting the API multiple times. 

 

You can't stop it from hitting it the exact number of times it's evaluated. So if X is the number of IDs and Y is the number of queries/references then the total number will be X*Y.

 

I have solved for this by introducing a dataflow to hit the API, and using power automate to trigger a dashboard refresh when that dataflow refreshes. 

View solution in original post

2 REPLIES 2
BladeLyfe
New Member

So there is essentially no way to prevent power bi from hitting the API multiple times. 

 

You can't stop it from hitting it the exact number of times it's evaluated. So if X is the number of IDs and Y is the number of queries/references then the total number will be X*Y.

 

I have solved for this by introducing a dataflow to hit the API, and using power automate to trigger a dashboard refresh when that dataflow refreshes. 

GilbertQ
Super User
Super User

Hi @BladeLyfe 

 

You could try the Table.Buffer, or what if you had to output each API call to a seperate table and then join them later in steps?





Did I answer your question? Mark my post as a solution!

Proud to be a Super User!







Power BI Blog

Helpful resources

Announcements
Join our Fabric User Panel

Join our Fabric User Panel

This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.

June 2025 Power BI Update Carousel

Power BI Monthly Update - June 2025

Check out the June 2025 Power BI update to learn about new features.

June 2025 community update carousel

Fabric Community Update - June 2025

Find out what's new and trending in the Fabric community.