DM_GWPipeline_Gateway_CanceledError

[Victor_V]

Hi,

As of yesterday we are having a large number of dataset failures, all with the same error message: 

DM_GWPipeline_Gateway_CanceledError

We restarted our on-premise gateway services as well as the servers they are running on, but the problem persists. Our source systems are fine, no changes were made in the last 24 hours, we're using the latest gateway version and some datasets are still refreshing without issue. So there is no consistent line to drawn in where the issue may lie.

A high priority ticket was logged to Microsoft, but we wanted to check here as well in case this is something other people have run into in the past as well. 

Thanks in advance!

[Anonymous · Accepted solution]

Hi @Victor_V ,

This issue has now been resolved, thank you for your patience!

Best Regards,

Xianda Tang

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

[awright19]

Is there any information on what the issue was or how it was solved? We (and others based on my post: https://community.fabric.microsoft.com/t5/Service/Intermittent-DM-GWPipeline-Gateway-CanceledError/m...) are having the issue currently.

Angie

[Anonymous]

Hi @Victor_V ,

This issue has been confirmed as a known issue internally. Please be patient to wait for fixing. If there is any news, I will update it here.

Best Regards,

Xianda Tang

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

[Anonymous]

Hi - just coming back on this issue... A member of my team managed to get the model refreshes working again this morning. He'd followed some suggestions in the link below and changed the PowerPlatformDataflow privacy level in settings.

Link: Solved: Re: DM_GWPipeline_Gateway_MashupDataAccessError - Microsoft Fabric Community

[Anonymous]

Hi - we started getting this error on Friday causing all the semantic models to fail but not the dataflows. We have been unable to fix it so far so pls keep us updated if you get a fix.

Thanks

Paul