Forum Discussion
PowerBI Premium Query Timeout
I put in a ticket but they're going down the "you don't have enough capacity even though we have a P2" path. So for now we are keeping the filters removed and hoping the fix for the custom visual situation fixes this too. We're also going to upgrade to the new Premium workspace architecture to see if perhaps it's in relation to that (IE - the stuff they're rolling out to the service now only works properly in the new architecture and they don't realize it's harming workspaces in the old architecture.) Did you check your filters to see if there are ones that might be able to be removed or retooled that will fix this for you?
Hi tctrout ,
I know that you mentioned Premium, and the following thread is not Premium (that I saw) but this might be helpful in your thinking process:
The XML for Analysis request timed out before it w... - Microsoft Power BI Community
Also, you might want to try the Performance Analyzer in desktop just to see what might be the issue in the Service: Use Performance Analyzer to examine report element performance in Power BI Desktop - Power BI | Microsoft Docs
And, perhaps take a look at this blog by Chris Webb:
Hello, thank you for the response.
I have read all the reference articles.
1. The first one focuses on Refreshing the data; my data model refreshes without error in under a minute, its a small .txt /.csv /.xlsx sources.
2. I leveraged the performance analyzer within the PBIX desktop and saw that the DAX queries could be optimized. However, locally within the PBIX the visual DAX Query will render in 30 seconds. When its published to the service, the visual will error after 225 seconds with the above error.
3. Chris Web's blog provided me the direction to post this specific question within the community. I have tried changing those setting outlined in his post but they did not make a difference. The odd thing is that it still errors out, stating a time out of 225 seconds where I know that I changed the settings to use more memory (50% of capacity) and increased time out to 7200 seconds.
It doesnt appear that any changes I make to our capacity will render that visual where at the beginning of last week it rendered fine and at the end it cannot render.
Hey tctrout ,
I also had a similar problem once, but, like you I increased my timeout and the world was a magic place after that. So, my experience went fine with the change. I am thinking this would be worth a ticket to Microsoft since they have the back-end service logs and can perhaps point you in the right direction. And, if they do, please let us know in this ticket the result so we can all learn!