dataset refresh stuck / Cannot be updated via ALM toolkit either

[spinachrice]

Hi all, 

Wonder if anyone had similar issue. We have a dataset published to a premium workspace, refreshing data from snowflake server via XMLA endpoint. It usually takes 15 min for the dataset to refresh, but yesterday around 12:00PM all of a sudden the refresh seems to be stuck. I cancelled the XMLA endpoint refresh, triggered a manual refresh from pbi service, still not progressing. No error but just stuck for over an hour. I cancelled that. Thought if i just refresh a small table from SSMS it should tell me if it's due to the size. Even the smallest table would not refresh. 

I then tried to update a measure from ALM TOOLKIT, and the deployment would not go through either. It just says committing changes on the bottom left of ALM toolkit for over an hour while usually this process takes 30 seconds. 

In the end i had to republish the same dataset again, and hasn't encountered any issues with the refresh of the new dataset. 

This is the 2nd time this has happened, and it has been causing quite a big disruption to our critcal reporting. 

Wonder if anyone know how to mitigate this or where i can get in touch with the power bi team for some support? 

Thank you

Yachee

[maygz]

Hi,

We've been facing the same challenge and MSFT hass been requesting lots of logs but no resolution. Only workaround seems to create a duplicate dataset, refresh it and repoint all the dashboards to this new dataset. Everynow and then, if the engineer is good one, they restart the capacity and it fixes the issue but usually this only happens by change as we are in an AEST timezone and the US based teams are not available.

Their support team has not been helpful as they are usually asking if the problem is solved and whether they can close the ticket (without ever coming back to a resolution or timeline for the fix). My team feels this is a product defect. 

We have Power BI Premium P3, use vNet Gateway and have Snowflake Private Link.

[spinachrice]

I forgot to mention, our data engineer also monitor the snowflake warehouse queries while i triggered the refresh, we confirmed that the query are not been sent to snwoflake at all. So it doesn't seems like a data warehouse capacity issue either. 

Same table from other dataset has been refreshed without any problem, and the query of other datasets are hitting the data warehouse. 

[maygz]

We have monitored the same way and have the same scenario. What is your set up of the data pipeline. i.e. Do you use vNet Gateway, Snow Private Link etc..? Has Microsoft come back you.. Any suggestion on a workaround?