Forum Discussion
Scheduled Refresh cancelled by system
Since 10-May-2021, we have started experiencing Scheduled Refresh getting cancelled and a failure notification being sent with the reason as "The scheduled refresh is cancelled because a new refresh is detected on the same database". But the refresh history do not have any other occurrence of the refresh at that time.
- FYI - We migrated to Premium Capacity in Apr-2021 and this has been repeatedly been observed for 2 specific Dataset refreshes (both within a same workspace).
- Related Support ticket is escalated & still being analyzed by the Power-BI Product Team but yet to receive a positive development.
Have any of of you experienced this problem in your Premium or PRO (shared capacity) service?
Would also appreciate any inputs / suggestion to get this resolved.
Thanks in advance !
5 Replies
- collinq
Super User
Hi ShankarS ,
I have seen something similar but not this exactly. Two thoughts - first, when you migrated did you do code migration of some sort or re-publish the report to the new site? My thinking is that if you didn't re-publish it as new to the new spot then it is holding on to something old. My second thought is something that I have run into a number of times - that the refresh from the data source kicks off with one report, but that report started later and/or goes longer than I expect (remember, the scheduled refresh time is the time that you would like it to start but not necessarily the actual start time) and then the next report gives me that type of message. It is not every time and it is not easily diagnosed but I know I have had that type of problem in the past.
Thank you for quick reply, collinq !
Our migration to Power-BI Premium involved migrating the required workspace(s) to Premium capacity.
- These 2 impacted datasets are part of 8 datasets that got migrated this way, in this workspace.
- Post Premium migration (in Apr-2021), one of these 2 has gone thru changes few times and new versions published while the other one has not undergone any changes in the last 5 months.
To clarify further on my earlier post -- the refresh history do not show any duplicate refreshses running at all (starting before or after the cancelled refresh) and that's why Product Support also seem to be taking time in their analysis.
- collinq
Hi ShankarS ,
So, there are NOT two reports running against the same database at the same time? That would be my first guess. I have had it happen where a report refresh kicks off, doesn't complete yet and the second report starts and then I get conflicts. But if that is not the case, then I am wondering if you have your Premium settings set to have more memory/capacity/processing high enough to prevent errors?
