Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.