Forum Discussion
Unexpected error: Evaluation was canceled
I'm facing the issue as well. It's quite annoying to refreshing all the query one by one each time I go to the Power Query editor, waste so much time.
I am facing the same issue now. I found one of possible reasons at Microsoft TechNet (https://social.technet.microsoft.com/Forums/en-US/f55b83a9-a966-46a4-80fc-2cca08fa3a12/unexpected-error-evaluation-was-canceled?forum=powerquery)
The answer says: "
Do you have background analysis disabled? If so, these errors can happen but should be purely cosmetic. The reason they happen is that the editor side pane depends on analysis results. If you mouse over one, this starts an on-demand analysis evaluation. If you then mouse over another one, the previously started on-demand evaluation will be canceled and show the error triangle.
Let me know if the errors interfere with the loading of your data to the workbook or data model. That would be a bug."
However, I am not sure what backgroud analysis means. I did uncheck the "Allow data preview to download in the background." I am wondering if this could be a reason why this error keeps happening?
I unchecked this to speed up the refreshing speed, since I am importing lots of CRM data from the datawarehouse. It would be painful if this is the root cause...
- Anonymous6 years agoNot applicable
I am experiencing the same problem getting the 'Re: Unexpected error: Evaluation was canceled' error, and I also can correct this by retrying each of the failed queries, which as others have mentioned is annoying and time consuming. However I can also see evidence that this is more than just cosmetic. Before I re run the queries I noticed that there was missing data in my report, and after re running the failed queries the data appeared.
What concerns me the most is that my report, by my own standards is reasonably complex, but it only consists of 16 queries, and it is getting the data from CSV which has less than 200K rows, and is only about 70MB in size. Power BI boasts about being able to deal with large amounts of data, running into millions of rows, but what I am doing is already bringing it to it's knees.
It might be that i need to get better and more efficient with my query language, and for Power BI's sake I hope this is the case.
- zzzzoooo6 years agoFrequent Visitor
I've never run into this problem until I uncheck the option ""Allow data preview to download in the background." in the Query option. So, this problem might be related to that option or 'Fast Data Load'.