Intermittent DM_GWPipeline_Gateway_CanceledError

[awright19]

We have had a string of refresh failures due to the DM_GWPipeline_Gateway_CanceledError error over the last week or so. The dataset affected varies. Most are scheduled refreshes, but it has happened on manual refreshes as well. Generally, when manually starting the refresh again, it works fine. The sources are working fine in other datasets.

Any idea what could be causing this?

[v-pnaroju-msft]

Hi awright19,

Thank you for your response and confirmation. We sincerely apologize for any inconvenience caused.

For any future queries, kindly contact the Microsoft Fabric community. We will be glad to assist you.

Thank you for your understanding and cooperation.

[v-pnaroju-msft]

Hi awright19,

We are following up to ascertain whether your query has been resolved through the use of the gateway cluster. If the issue has been resolved, we kindly request you to share the details with the community to help others who may be facing similar challenges.

As this thread has remained open for a considerable duration, please note that if we do not receive a response, in accordance with community guidelines, we shall proceed to close this thread. For any further discussions or new queries, you are welcome to initiate a fresh thread on the Microsoft Fabric Community Forum, where we will be happy to assist you.

Thank you for your cooperation and understanding.

[awright19]

As I mentioned in my post the other day, we do not have the resources to set up a cluster at this time. We are on the latest gatway.

Please close the thread, just as we closed the ticket.

[v-pnaroju-msft]

Hi @awright19,

Thank you for the update and apologies for the inconvenience caused.

We are following up to check the status of the following:

1. Have you had the opportunity to work with your network team to resolve the issue using the gateway cluster? If yes, kindly provide the details that could be helpful to the community.
2. Have you tried using another machine, and are you still facing the same issue?
3. Have you upgraded to the latest version of the gateway and verified if the issue persists? Please also confirm the current gateway version you are using.

Thank you.

[v-pnaroju-msft]

Hi awright19,

We are following up to check whether the support ticket raised from your end has provided a resolution to the issue. If it has, we kindly request you to share the solution with the community and mark it as the accepted solution, as this will assist others facing similar challenges and benefit the broader community.

Thank you.

[awright19]

The issue is not resolved. However, we closed the support ticket because we weren't getting anywhere and the failures have been occurring much less often. Support kept changing their recommendation and not following through on things they did suggest. At one point they shared a screenshot of charts that apparently supported their recommendation, but that screenshot was blurry and unreadable and when asked if they could provide one that was readable, we were told they didn't have access to that. Which is ironic for a data visualization program.

At some point, we'll try the cluster option they suggested, but we don't have resources for that at the moment.

[v-pnaroju-msft]

Hi awright19,

Thank you for the update. We kindly request you to keep us informed about the issue, as it may be beneficial for other members of the community facing similar concerns.

Thank you.

[awright19]

We are being told to install a gateway cluster. Has anyone else been told that? Curious if anyone has done it and if it's made an impact.

[victor_mirante]

We were indeed experiencing this error with the cluster. The errors stopped when our network team allowed some IPs that were showing failures in the logs generated by the gateway. They also fixed the communication route for the link. It's been two weeks since we've had this error.

[v-pnaroju-msft]

Hi victor_mirante,

Thank you for your update and for sharing your insights and approach in stopping the error.
Your findings could be valuable to other community members facing similar connectivity issues, especially those related to gateway failures and network routing.

Thank you.

[awright19]

I appreciate the information!

[v-pnaroju-msft]

Hi awright19,

Thank you for your response. We kindly request you to keep us informed about the issue, as it may be beneficial for other community members facing similar concerns.

Thank you.

[YunierG]

Hi again, anyone have some response from microsoft?
only read some post similar the solution was rollback to September 2024 Gateway is the correct solution?

searched the incident if was fixed but is removed, don't understand.

Link to the microsoft have the issue removed:
Known issue - Intermittent refresh failure through on-premises data gateway - Microsoft Fabric | Mic...

[victor_mirante]

Hello everyone,

After several tests with Microsoft, our network team discovered an issue with the communication route to the link. I’m not able to explain it very well since I'm not part of the network team, but after we fixed this route, the errors significantly decreased. It’s still not 100% error-free, but it's much better.

We also shared the gateway logs with Microsoft, and they asked us to whitelist some IPs, as they were showing failures in the log.

They suspect that the issue is indeed related to the gateway version. This is all we've discovered in the past few days.

[YunierG]

Thank's for the information @victor_mirante , our organization is testing and monitoring update april 2025( the update was applied 30th April), i will comment later, with news.

[YunierG]

Hi, today review, with april 2025 desktop & Gateway, the porcentage low but persist error sometime daily.
I still wait new version for test.

[awright19]

We continue to see the issue on a daily basis. Microsoft is still investigating.

FYI, the issue mentioned in the link you included is for a different error. The error we get is the DM_GWPipeline_Gateway_CanceledError error.

[YunierG]

Thank's, @awright19  for the information.
yes, wrong Link and error, our error on gateway is other.

[v-pnaroju-msft]

Hi awright19,

Thank you for your valuable update. We kindly request you to keep us informed about the issue, as it may be beneficial for other community members facing similar concerns.

Thank you.

[ezaidi]

Any update on this issue? It has been two and half months of this headache and not resolution on our end. Has anyone heard back from MS with regards to this?

We have done all the basic troubleshooting on our end as mentioned in many of the other threads on here.