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

Be one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now

Reply
Masakinka
New Member

Timeout Issues in Power BI - Need Help Resolving Visual Loading Error

Hi everyone, 

I'm facing a challenge with a timeout error in a published Power BI report using the DirectQuery mode. While everything runs smoothly in the Power BI Desktop version, the published report fails to load certain visuals, showing the following error message:

Couldn't load the data for this visual.
Timeout expired. The timeout period elapsed prior to completion of the operation. The exception was raised by the IDbCommand interface.

 

The queries involved typically take about 7 minutes to complete in desktop mode. Here are some general settings I'm working with:

  • License Type: Premium Per User

I'm looking for insights on how to address this issue, particularly if it's related to the DirectQuery performance or potentially a timeout setting that needs adjustment under the Premium Per User license.

Any advice or suggestions would be greatly appreciated!

Thank you!

1 ACCEPTED SOLUTION
v-kaiyue-msft
Community Support
Community Support

Hi @Masakinka ,

 

Thanks for the reply from @SaiTejaTalasila , please allow me to provide another insight: 

 

DirectQuery sends all requests to the source database, so the time it takes for a visual to refresh depends on how long it takes the underlying source to return results. Five seconds or less is the recommended response time to receive the data requested by a visual. Refresh times longer than 30 seconds create an unacceptably poor experience for people using the report. In the Power BI service, queries that take longer than four minutes time out and users receive an error. This limit is designed to prevent issues caused by long execution times. You should only use DirectQuery for sources that can provide interactive query performance.

 

You can start diagnosing performance issues in Power BI Desktop, not in the Power BI service. Performance issues are often based on the performance of the underlying source. It's easier to identify and diagnose issues in a more isolated Power BI Desktop environment.

 

More detailed information is available in the documentation:

Use DirectQuery in Power BI Desktop - Power BI | Microsoft Learn

DirectQuery in Power BI - Power BI | Microsoft Learn

 

If your Current Period does not refer to this, please clarify in a follow-up reply.

 

Best Regards,

Clara Gong

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

View solution in original post

3 REPLIES 3
v-kaiyue-msft
Community Support
Community Support

Hi @Masakinka ,

 

Thanks for the reply from @SaiTejaTalasila , please allow me to provide another insight: 

 

DirectQuery sends all requests to the source database, so the time it takes for a visual to refresh depends on how long it takes the underlying source to return results. Five seconds or less is the recommended response time to receive the data requested by a visual. Refresh times longer than 30 seconds create an unacceptably poor experience for people using the report. In the Power BI service, queries that take longer than four minutes time out and users receive an error. This limit is designed to prevent issues caused by long execution times. You should only use DirectQuery for sources that can provide interactive query performance.

 

You can start diagnosing performance issues in Power BI Desktop, not in the Power BI service. Performance issues are often based on the performance of the underlying source. It's easier to identify and diagnose issues in a more isolated Power BI Desktop environment.

 

More detailed information is available in the documentation:

Use DirectQuery in Power BI Desktop - Power BI | Microsoft Learn

DirectQuery in Power BI - Power BI | Microsoft Learn

 

If your Current Period does not refer to this, please clarify in a follow-up reply.

 

Best Regards,

Clara Gong

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

SaiTejaTalasila
Super User
Super User

Hi @Masakinka ,

 

It looks like the backend which are generated by your visuals on service are taking more time to execute.

 

 

Thanks,

Sai Teja 

Hi @SaiTejaTalasila,

Thank you for your input. I understand that the backend processes for my visuals are taking longer than expected. Could you advise if there's a way to adjust the timeout settings specifically for DirectQuery in the Power BI service? Any guidance on where these settings might be managed within the Power BI portal or if there are other best practices to handle such timeouts would be greatly appreciated.

Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!

ArunFabCon

Microsoft Fabric Community Conference 2025

Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.

December 2024

A Year in Review - December 2024

Find out what content was popular in the Fabric community during 2024.