If there are any performance issues in database this would lock down the table...
I even observed that reports doesnt get published until the refresh is done...
Agree with Miguel Ulloa. Cancelling a refresh should be v1 capability. This is the biggest issue our team faces. A user publishes a bad report that takes down our Enterprise Gateway servers and impact our entire platform. We used to use SSMS to query the dataset and run a query to kill it, but it retries 3 times, which takes more than an hour. We now find we can no longer do this. We currently have no way to kill the refresh and have to wait 5 hours for it to kill itself. I have been patient for this capability and just because it does not meet your vote count to work on it, does not mean this is not a large issue with your design. You are not going to get the high number of votes because the support teams are the main people this impacts, not the masses. Please prioritize this.
Just add a button to the interface to stop a refresh. Give it a few warnings messages before proceeding. It's already something that can be done with Dataflow refreshes. Not sure why it's not an option in datasets.
A pretty basic request. That is ridiculously not available. The API calls don't even work to do the same. Disappointed. Please fix.
There's an API for this, isn't there?
Just set off two refreshes due to the same update. The smaller one failed already. I've already identified the fix.
The "big" refresh will eventually fail, but I'm sat here waiting for it to do so so I can finish applying the fix. The lack of a cancel on the refresh is holding me up.
Considering there are third-party companies designing APIs specifically to fix this one issue, it's clear that MS is well aware of the problem. Some users have commented that there was a feature that allowed users to cancel the infinite refresh, but that this feature has been removed. When will this problem be escalated?
I run Power BI for my company, if I refresh my dataset an publish (due to a model change or the like), I need to refresh the desktop file.
When I've then published it, the Power BI service then refreshes it again ?!? We run on Power BI pro licences only
I mean, this functionality WAS PRESENT so why did it go away?
I have a refresh that is taking 210 minutes with maybe 2.3 Mb of data in the model.
Why is this under "needs votes"? Just how many votes does it need? This is a critical feature to be able to maintain sanity of the workspace where some datasets might be misbehaving causing a domino effect on the rest of the scheduled reports.
Administrator on 12/7/2022 10:22:57 PM
Update 12/7/22 - Announced