DM_GWPipeline_Gateway_MashupDataAccessError

Hi rafaelr08,

Thank you for bringing this to the community, and a big appreciation to Akash_Varuna for sharing such a precise and helpful response!

As mentioned, the error DM_GWPipeline_Gateway_MashupDataAccessError is commonly linked to transient encryption or connectivity issues, particularly during scheduled refreshes involving Lakehouse or SQL-based sources. The super user has correctly highlighted the key factors and best practices to mitigate this.

Here are a few additional suggestions:

Use the refresh history and Fabric monitoring tools to identify if the error occurs at specific times or under load, which can help pinpoint service-level delays.

If multiple models or datasets are refreshing concurrently, consider staggering the schedules to reduce potential service contention.

If you're working with large volumes of Lakehouse data, explore Enhanced Refresh (if available in your workspace), which improves reliability through chunked data refresh and retry logic.

Since your source is a Fabric Lakehouse, gateway checks may not apply unless your model pulls data from external or hybrid sources. But if any other connections exist via on-premises gateways, ensure SSL certificates and trust chains are valid and up to date.

If this solution worked for you, kindly mark it as Accept as Solution and feel free to give a Kudos, it would be much appreciated!

Regards,

Sahasra

Customer Support Team – Microsoft Fabric Community.