March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
I have a dataflow setup for a long time which refresh UK morning time. Over the last few days, the refresh is failing with strange timeout error. Yesterday, the refresh failed after 30mins, with the error below. The dataset on which the I got the error was only executing for 1min and 30.9secs.
Error: The operation is timed out. Request ID: a09e3682-e741-4535-883b-7960347285cf Activity ID: c9b7e823-5720-44da-ba80-4df20f802041
I manually started the refresh and it completed successfully.
Today again the refresh failed with the following error after 44mins. This time on a different dataset which was executing for 1mins and 30.6secs.
Error: The operation is timed out. Request ID: b8cd8430-cdaf-4cfd-88e9-94f69122f272 Activity ID: 0c3fc6f8-2ae3-4143-95d7-bfbfedbe97ef
I started a manual refresh and it failed with the following error after 10mins. this time failing on a third dataset which was executing for under 2mins.
Error: The operation is timed out. Request ID: c495e34f-65db-5cac-a7d1-a666dcedc1c0 Activity ID: dfef7704-dc81-4347-ab5e-e1e1b39885de
How do we findout where is the problem - is it a problem on the gateway or on the PowerBI service?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If your dataflow is in the premium workspace, see this known issue document:
Known issue - Long running, failed or stuck dataflow in Premium Gen2
As a last resort, you can try swapping the workspace out of Premium to Pro and wait a few minutes. Then switch the workspace back to Premium. This solution may help to provide relief, but the issue could reoccur.
Information on the support page:
https://powerbi.microsoft.com/en-us/support/
Engineers have identified multiple root causes and expect a first improvement of the experience to be deployed by end-of-day 06/30/2022. A next major wave of fixes is expected to be deployed by end-of-day 07/21/2022.
Best Regards,
Community Support Team _ Yingjie Li