Forum Discussion
Power BI Datamart
Hello,
I have a Datamart that has been refreshing for over 24 hours. It typically takes 5-10 minutes to refresh, and I had already sucessfully refreshed it prior that morning.
Is there any way to cancel this refresh?
Thanks
Hey fvalento2023 ,
On the Datamart, you can open the Dataset that you want to stop the refresh by clicking on the elipses and then select the "Schedule Refresh" and select "Cancel Refresh" there.
7 Replies
- collinqSuper User
Hey fvalento2023 ,
On the Datamart, you can open the Dataset that you want to stop the refresh by clicking on the elipses and then select the "Schedule Refresh" and select "Cancel Refresh" there.
- fvalento2023Helper I
This is not an option for Datamarts....
- collinqSuper User
- fvalento2023Helper I
I was able to get the refresh to stop spinning, by clicking schedule refresh, then manually turning the schedule refresh off.
However after I tried to manually refresh again it pretty much immediatley fails, which brings me to potentially what the root cause of the issue.
Any suggestions on how to troubleshoot this?
- AnonymousNot applicable
You are right fvalento2023, there is no way to stop a datamart, not even Microsoft Support partners can do this currently.
We are having a similar issue with a process that normall takes 2-3 minutes, you just need to raise a PBI Support ticket and hopefully they will pass it through to the Product Team to investigate.
Through a process of elimination, we believe there's sometimes an issue between the Power BI Service and the Azure backend database (provided by Microsoft, behind the scenes) where the datamart is locked but not actually accessing any data sources.
In our case it can take several hours to finish, although last Monday morning it failed (which means annoyingly you can't view a log, yesterday morning it completed after several hours. When we checked the successful refresh log, we found two data extracts we take from another PBI datamart had taken several hours but everything else had completed within 2 mins - we were left wondering whether this had caused some sort of conflict/DB lock but without access to the Azure database behind PBI we can't see anything more.