Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
Hello everyone,
We have been having massive problems with our semantic model updates since 20.5.2025. The data is mainly served via gateway from an on prem SQL server. On average, the models take about 15 minutes, but sometimes much longer, e.g. 1.5 hours, then 15 minutes three times in a row, then 45 minutes, etc.
We have a premium per user license, so that a noisy neighbour issue should be excluded. We have also had no fundamental changes since 20.5.2025. The problems came from one day to the next.
We had such issues about 2 years ago and it was clearly due to the gateway because Microsoft (confirmed by Microsoft Support) had problems with the gateways at that time. My guess is that this time it could also have something to do with it, because the last gateway update was on 21.5.2025 and the error message was the same as 2 years ago:
Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding
Does anyone here in the forum have similar problems?
Best regards and thanks
Stewwe
Solved! Go to Solution.
Hi @Stewwe ,
This could be an intermittent issue. If it occurs again, please start a new thread in the forum. We will address it as soon as possible.
Thank you.
Hi @Stewwe ,
This could be an intermittent issue. If it occurs again, please start a new thread in the forum. We will address it as soon as possible.
Thank you.
Hello @v-venuppu,
our problems have resolved themselves. Since we have not changed anything significant, the gateway is once again under suspicion. Doesn't really make us happy because we know that the issue will come back to us in a few weeks or months.
Thank you all for your feedback 🙂
Hi @Stewwe ,
Thank you for reaching out to Microsoft Fabric Community.
Thank you @Ilgar_Zarbali @Madalina2801 @Poojara_D12 @collinq for the prompt response.
I wanted to check whether Have you had a chance to raise a support ticket as suggested by @Ilgar_Zarbali and resolve this issue? If so, please consider sharing the solution in the forum and marking it as accepted, this will help other members find the answer more easily.
Thank you.
Hey @v-venuppu ,
Hello,
we are still in contact with Microsoft Support. So no news yet.
I will post the result when the issue has been resolved.
Kind regards
Hi Stewwe,
Yes, you're not alone—several users have reported similar gateway-related performance issues since the May 21, 2025 update. The sudden increase in refresh time and `Execution Timeout Expired` errors suggest it may be tied to that latest gateway version.
Here are a few quick suggestions:
Hopefully, Microsoft will release a fix or hotfix soon. You're doing the right thing by checking with the community.
Did the issue appear after upgrading to May version 3000.270.10? I'm also curious if the issue is related to this version because we're not sure if it's ok to upgrade to this version. I saw another post last week Gateway issues - Microsoft Fabric Community.
Hello Madalina,
we got the problem on 20.5.25 with the gateway version 3000.258.5 and then tried to update the gateway to the latest version 3000.270.10
However, I still believe that it is the gateway- regardless of the version- as we suddenly have these random loading times. We load two data models separately from two different SQL servers and both models suddenly have these problems.
Hi @Stewwe
Since May 20, 2025, you've been experiencing severe instability with your Power BI semantic model refresh performance, which relies on data served through an on-premises SQL Server via a data gateway. Normally, your refreshes take around 15 minutes, but you've observed erratic behavior where the same models occasionally take over an hour or more to complete without any clear cause—despite no significant changes on your end. Given that you're using a Premium Per User (PPU) license, typical resource contention from other tenants (often called "noisy neighbor" issues) should not be the root cause. What's notable is the timing: the last gateway update occurred on May 21, 2025, just a day after the issues began, and the error message you're receiving—“Execution Timeout Expired…”—is the same one you encountered during a known gateway issue confirmed by Microsoft support two years ago. This strongly suggests that the problem could again be related to a faulty gateway update. You're not alone in suspecting this, as others in the community have reported similar inconsistencies around gateway performance following certain updates. It would be helpful to check whether others in Microsoft support forums or the Power BI community have raised similar cases recently. In the meantime, monitoring gateway logs, reviewing SQL Server performance counters, and potentially rolling back to a previous gateway version (if possible) could help isolate or temporarily mitigate the issue until Microsoft confirms and addresses any bugs in the latest update.
HI @Stewwe ,
I have not heard of issues but I guess it is feasible that some folks' environment doe not work well with the latest update. I looked up the known issues and there are none that I saw about the gateway.
I think that your choices are to either contact Microsoft and see what they can see. Or, you could uninstall and reinstall an older version of the gateway. if you have the recorvery key this should not be a problem. See this article on how to do it: Migrate, restore, or take over an on-premises data gateway | Microsoft Learn
Proud to be a Datanaut!
Private message me for consulting or training needs.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
60 | |
32 | |
27 | |
22 | |
22 |
User | Count |
---|---|
63 | |
49 | |
28 | |
24 | |
19 |