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

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Dashboard update timeout / problem hosting the mashup engine

Hello, everyone.

I'm using Power BI pro. Since last 2 weeks most of my reports can't be updated successfully on Saturday and Sunday. This update error occurs mainly on these 2 days in a week. Type of error:

The last refresh attempt failed because of an internal service error. Before the data import finished, its data source timed out.

I've also analyzed logs of gateway and there was an error type:

TemplateMessage: A problem hosting the mashup engine was detected. Reason: Timeout.

 

For example, this report is normally updated in 12-15 minutes. The report contains of simple cloud data sources: google sheets and pbi dataflow; 2 mb data model without hard measures.

analyticrequest_0-1668683092109.png

What else can I do and check to fix this error?

I will be grateful for your recommendations)

 

Status: Investigating

Hi @analyticrequest ,

 

 It sounds like you data source is too slow for direct query and it throws a timeout before solving the visualization. Direct Query can't be applied with every database engine or scenario. 

I always recommend using import data to my users except for really specific scenarios or requirements because it's not that easy to make it work properly.

Related link about Direct Query:

Limitations: https://docs.microsoft.com/en-us/power-bi/connect-data/desktop-use-directquery#limitations-of-direct...

Implications: https://docs.microsoft.com/en-us/power-bi/connect-data/desktop-directquery-about#implications-of-usi...

Design Model for Direct Query: https://docs.microsoft.com/en-us/power-bi/guidance/directquery-model-guidance

 

Best regards,

Community Support Team Selina zhu

Comments
v-mengzhu-msft
Community Support
Status changed to: Investigating

Hi @analyticrequest ,

 

 It sounds like you data source is too slow for direct query and it throws a timeout before solving the visualization. Direct Query can't be applied with every database engine or scenario. 

I always recommend using import data to my users except for really specific scenarios or requirements because it's not that easy to make it work properly.

Related link about Direct Query:

Limitations: https://docs.microsoft.com/en-us/power-bi/connect-data/desktop-use-directquery#limitations-of-direct...

Implications: https://docs.microsoft.com/en-us/power-bi/connect-data/desktop-directquery-about#implications-of-usi...

Design Model for Direct Query: https://docs.microsoft.com/en-us/power-bi/guidance/directquery-model-guidance

 

Best regards,

Community Support Team Selina zhu

analyticrequest
New Member

@v-mengzhu-msft hi, friend!) Thank you for your responce. I'm not using direct query in this report (only import) and data source loading can't be too slow, because there are some super simple tables in sources without any types of merges. In PBI desktop this reports updates normally in 2-3 minutes, in cloud - 12-15 min.

analyticrequest
New Member

I've activated additional logging in gateway. I've found one more type of error, that sounds like:

An internal error happened due to failed runtime assertion: Failed to get MWC token

analyticrequest_0-1669187757373.png

I see this type of error also only on Saturday and Sunday.