Spooling failed with error: The operation failed due to an explicit cancellation.

Hi lbendlin 

Do you have any tickets yet?  I am hoping there is a configuration somewhere to prevent the implicit retries when the spooling errors happen.  That would at least avoid the unintended impact on the back-end systems.  I don't want our back-end systems to suffer, because of some bugs in the Power BI dataflow refresh operations.

I'm guessing that the Microsoft product team will want to blame this on random network glitches (ie. solar flare from outer space).  But I don't really buy it.  The TCP protocol is extremely fault-tolerant, and is able to recover from lots of networking problems.  The failures in this service seem like they are more likely to be  related to software bugs and/or design flaws.

It happens a lot more frequently than you would expect.  In fact, the Mindtree engineer asked me to turn on enhanced logging, and we captured one of these happening on the first day, during the first three refresh operations.

I suspect the Microsoft team already has a way to monitor my gateway for the health of the network, and can rule out any obvious problems with network health.  Aside from Microsoft, I suppose the only other component where I might put the blame is the Zscaler team.  Perhaps there is an outbound NAT issue which only affects Power BI.

The main problem is that there are virtually no meaningful errors in my logs, and Microsoft hasn't been willing to share anything from their side yet. 

Hi lbendlin 

Even if we don't know the reason for the spooling error itself, perhaps we can focus on the subsequent retries.  Have you ever worked with Microsoft to explain the implicit retries?

Those retries can do more harm than good.  We do NOT want repeated attempts to retrieve data from our data sources.  This would apply to 95% of ouf PBI dataflows and datasets.

... If ever the repeated attempts become necessary, we'd like to be able to configure those ourselves in a manual way.