Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
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.
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
37 | |
30 | |
17 | |
16 | |
8 |
User | Count |
---|---|
48 | |
40 | |
33 | |
17 | |
14 |