Forum Discussion
Data Refresh error: "DM_GWPipeline_Gateway_CanceledError"
- 1 year ago
Hi sandy_ew ,
Thank you for reaching out to us on the Microsoft Fabric Community Forum.
Before it was a known issue but is resolved now .Please try to refresh it again and check it once.If you still face the same issue please raise a support ticket.
If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.
Regards,
Menaka
Our organization started experiencing this issue last week and we are seeing around 100 failures daily. Whenever we manually re-trigger the refreshes, they always succeed. It is only scheduled refreshes that (intermittently) have this problem.
Anyone have any solutions?
- two_sandy1 year agoFrequent Visitor
[same message as my other issue]
I have again stopped experiencing this issue but it's the result of nothing I've done my end.
Initially I had heaps of errors occurring for the automated data refreshes, but not when I manually refreshed my data model (similar to how you describe your issue). The errors stopped some time after I raised this case (under another profile). They then occurred a few times again about a fortnight ago but I've not had one happen since then.
I wish I could tell you what the issue was / is.
- GilbertQ1 year ago
Super User
Is it happening with a Gateway or not?
If it is a Gateway please make sure it is running the latest version of the Gateway software?
- ConfusedPBIUser1 year agoFrequent Visitor
It is via the on-premise data gateways and it is on the latest version (February 2025).
- awright191 year ago
Advocate II
FYI, there is a newer update from March 12. We just installed it and so far so good. It's only been since last night, so I'm not calling it fixed yet, but we'll see.
- awright191 year ago
Advocate II
We just installed the latest gateway in the hopes that it will resolve the issue. Will keep you updated.
FYI, for us it has been both scheduled refreshes as well as some manual refreshes.
- ConfusedPBIUser1 year agoFrequent Visitor
We updated to the latest version last week and saw no difference. The Microsoft engineer also told us beforehand that it was unlikely to fix the issue since the February gateway version only had minor updates. He said the March version should have more changes and might resolve the issue.