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.
Please provide option to stop refreshing dataset after refreshing manually... If there are any performance issues in database this would lock down the table... I even observed that reports doesnt ...
