Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowData Days is here! Join us now for 60+ days of learning, challenges, and connection. Learn more
Hello, for approximately 4 days now, the online data set has not been updated and the following error is displayed:
{"error":{"code":"DM_GWPipeline_Gateway_TimeoutError","pbi.error":{"code":"DM_GWPipeline_Gateway_TimeoutError","parameters":{},"details":[],"exceptionCulprit":1}}} Table: XXXX
We have conducted various tests, updated the gateway and the table updates correctly from Power BI Desktop.
However, when attempting to update it from the Power BI service it returns an error.
Can someone please assist us with this issue as it is affecting our business?
There have been no changes applied, so we do not understand what could have happened.
The rows have remained the same.
Thanks a lot
Solved! Go to Solution.
Hi. What sources does your semantic model get? how much it takes before the refresh fails? is it seconds or 10 minutes?
This issue can be because your data is growing and now it can't refresh it during the timeslot you have by default with PowerBi (it can be changed) or the data source is so busy when the refresh is triggered that it can't reply the query as fast as the timeslot it has for returning it.
There are two timeouts, the one that shows when it's taking too long for connecting the source (connectionTimeout) and the one that takes too much for getting the result of the query or table (commandTimeout).
Let's see your answers about source and times to check if we can do something about that.
Of course there could also be an issue with bandwidth.
I hope that helps,
Happy to help!
Hi. What sources does your semantic model get? how much it takes before the refresh fails? is it seconds or 10 minutes?
This issue can be because your data is growing and now it can't refresh it during the timeslot you have by default with PowerBi (it can be changed) or the data source is so busy when the refresh is triggered that it can't reply the query as fast as the timeslot it has for returning it.
There are two timeouts, the one that shows when it's taking too long for connecting the source (connectionTimeout) and the one that takes too much for getting the result of the query or table (commandTimeout).
Let's see your answers about source and times to check if we can do something about that.
Of course there could also be an issue with bandwidth.
I hope that helps,
Happy to help!
Hi,
thanks a lot, your topics helps me to resolve the problem.
This reply doesn't give any hints to anyone coming later trying to solve the same issue.
Don't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.
Check out the May 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 16 | |
| 11 | |
| 10 | |
| 8 | |
| 7 |
| User | Count |
|---|---|
| 41 | |
| 36 | |
| 36 | |
| 28 | |
| 20 |