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

Don't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.

"Structural Change" errors resulting from Enhanced Refresh API

For the past couple months, our users have frequently encountered errors like the following:

 

Underlying Error: PowerBI service client received error HTTP response. HttpStatus: 400. PowerBIErrorCode: QueryUserError
QueryUserError: Current session is no longer valid due to structural changes in the database.

 

These errors prevent access to the report for a few minutes up to about 30 minutes.

 

After a lot of troubleshooting, the issue has been traced to model refresh executing through the Enhanced Refresh API. A workaround has been found by executing an XMLA Clear Cache command. This suggests that the API refresh command does not clear cache on its own, as other types of refresh do. Since we have not changed anything, it also suggests that this is new behavior, and is maybe not intended. Can you confirm whether Enhanced Refresh API clears the model cache, or whether it should? Thanks

Status: Investigating

Hi @nicg ,

 

Based on the above information, this issue is complex which may need to collect log files for further troubleshooting. Since community support engineers don't have that access, I would suggest opening a Support Ticket. If you are a Power BI Pro or Fabric licensee, you can create a support ticket for free and a dedicated Microsoft engineer will come to solve the problem for you. 
It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.

 

The link of Power BI Support: Support | Microsoft Power BI

For how to create a support ticket, please refer to How to create a support ticket in Power BI - Microsoft Power BI Community

 

Best Regards,
Community Support Team _ Caitlyn

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

Hi @nicg ,

 

Based on the above information, this issue is complex which may need to collect log files for further troubleshooting. Since community support engineers don't have that access, I would suggest opening a Support Ticket. If you are a Power BI Pro or Fabric licensee, you can create a support ticket for free and a dedicated Microsoft engineer will come to solve the problem for you. 
It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.

 

The link of Power BI Support: Support | Microsoft Power BI

For how to create a support ticket, please refer to How to create a support ticket in Power BI - Microsoft Power BI Community

 

Best Regards,
Community Support Team _ Caitlyn