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?
We had this problem starting yesterday with one report (and never before and we haven't changed anything.) When we publish it to a non premium capacity workspace it works fine... Once we got rid of the filters that were in essence just hiding blank rows it was fine on the premium service. However since this just started yesterday AND the other things that started yesterday too (Custom visuals dissappearing from the app) my hunch is it's related to a group of servers that host the app and premium capacities - perhaps a load balancer or something. Have you tried publishing it to a non premium service and see whether it works?
I am not able to test on a non premium capacity as this is not permissible within our organization.
Same scenario though, it stopped working with no changes made to the file where it had been working for several months.
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?
I never found an answer to this, but I suspect what you are outlining. We too have a P2 node so increasing the capacity settings should have been more than enough to resolve this timing / memory issue.
We optimized the DAX and it resolved the issue.