Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.

Reply
VickyMarga
Frequent Visitor

GWPipeline_Gateway_TimeoutError

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

1 ACCEPTED SOLUTION
ibarrau
Super User
Super User

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,


If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Happy to help!

LaDataWeb Blog

View solution in original post

3 REPLIES 3
ibarrau
Super User
Super User

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,


If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Happy to help!

LaDataWeb Blog

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.

Helpful resources

Announcements
September Power BI Update Carousel

Power BI Monthly Update - September 2025

Check out the September 2025 Power BI update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

Find out what's new and trending in the Fabric community.

Top Kudoed Authors