Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Hello: So I have published some files from Power BI Desktop to Power BI/0365. I entered my credentials, etc and for the last two days, was able to schedule the datasource(s) to refresh automatically. Nothing has changed within my .pbix file. This morning, I checked the dashboard and saw that nothing was refreshed. I manually tried refreshing the datasource, and it errors out.
One of the error messages that are returned is that it says the operation was cancelled by the user. However, I did not cancel the operation, so not sure why it says that.
I'm able to refresh the data/data source within Power BI Desktop, but again, it errors out when publishing.
Any help would be appreciated!
Thanks
Hi There
i am having the same issue with my datasource not being able to refresh. i get this error:
| Cluster URI: | WABI-NORTH-EUROPE-redirect.analysis.windows.net |
| Activity ID: | 1c4ea9a4-cd1d-484e-a196-3106892a2b1d |
| Request ID: | 3e7bd065-1875-f121-2911-3dae290a5119 |
| Time: | 2017-02-20 10:10:27Z |
how long did the refresh run before the error ? Could be a timeout
do you have connections that use a gateway ? Was the gateway 'down' during the refresh
i received this 'canceled by the user' only once, the day after (until now) the refresh worked again.
Error messages are not very clear and I also had many problems with that before. I raised an issue/question to give more detailed error info.
Hello -yesterday the refresh would run for like anywhere between 5 and 10 seconds (with no errors). No connections that use a gateway by the way. I've been browsing the forum and have read that others have experienced similar issues. Interesting thing was that i created a 'test' pbix file (literally, just a pull from an excel file that has 3 values), and published it. I get the same error when refreshing that datasource too. Maybe it's an issue with Power BI service itself
anyone with a solution?
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!