Hi! I've had about 90 dataflows set up for a few months now. Last night all but 2 of them failed with error MashupException.ErrorThe two that succeeded were very small tables with less than 100 rows of data.I'm loading data from an on-prem SQL server, as well as an Excel-file from a Sharepoint folder (this one also failed).On-prem-server: Excel-file: Has there been any change in Fabric in the last 36 hours? best regards

I just noticed that one of my dataflows were still running (or parts of it, before clicking into it it just said "failed"). trying to load 5 rows of data and it has been running for 36 hours now... and no easy way to cancel it.When will you implement cancellation of dataflows?

Hi JE_test Thanks for using Microsoft Fabric Community. Apologies for the inconvenience that you are facing here. When using Microsoft Fabric Dataflow Gen2 with an on-premises data gateway, you might encounter issues with the dataflow refresh process. The underlying problem occurs when the gateway is unable to connect to the dataflow staging Lakehouse in order to read the data before copying it to the desired data destination. This issue can occur regardless of the type of data destination being used. For more details, please refer : On-premises data gateway considerations for data destinations in Dataflow Gen2. If you are using Microsoft Fabric through an on-premises data gateway, be sure to update to the latest version of the gateway. Some errors related to output destinations or queries might be resolved by upgrading the gateway and also this ensures that any updates to Fabric features and known issues are propagated through the gateway. For details please refer : Currently supported monthly updates to the on-premises data gateways. We're adding support to cancel ongoing Dataflow Gen2 refreshes from the workspace items view, timeline for the cancel feature, please refer : Cancel refresh support in Dataflow Gen2. I hope this information helps. Please do let us know if you have any further questions. Thanks.

I aggree. Gremlins everywhere in the MS backend codebase, it seems. 😁 Good to know the architecture of your pipeline, but the question was directed v-cboorla-msft because s/he wrote: The underlying problem occurs when the gateway is unable to connect to the dataflow staging Lakehouse in order to read the data before copying it to the desired data destination. sentence which, by its use of pronouns, means the data GW is trying to write to a Fabric destination after pulling data from the staging LH. In other words, he says this:GW-->staging LH-->back to GW-->any type of destination , so a roundtrip to the on-prem data GW which I find very very odd to do. I thought the more logical and efficient path, after having loaded the data from the on-prem DB via the GW would be as follows: GW-->staging LH-->pipeline or dataflow (no more going back to the on-prem GW)-->destination (LH or DW) If the latter, then v-cboorla-msft explanation makes no sense, no offense Boorla. 😉

When staging is enabled and On Prem Data Gateway is used, the data will flow as such: 1. [Data Source] ---OPDG---> [Staging Lakehouse]2. [Staging Lakehouse] --- OPDG ---> [Final Output] It may not be the most optimal path, hence if you do not need staging of entities, please turn it off. Without staging, the path should simply be [Data Source] ---OPDG---> [Output]

You can click thisto go into more details, hopefully it has the error text. A refresh from Jan is too old for us to look into anyway (we only maintain logs for 28 days). If you can still reproduce this error, please do the following: 1. Turn on Additional Logging on the Gateway to obtain Mashup logs, then refresh and produce this error, then export the logs2. Send me the logs and request ID of the failure.

Dataflow refresh started failing today MashupException.Error

26 Replies

JE_test
Resolver I
2 years ago
I just noticed that one of my dataflows were still running (or parts of it, before clicking into it it just said "failed"). trying to load 5 rows of data and it has been running for 36 hours now... and no easy way to cancel it.
When will you implement cancellation of dataflows?
- v-cboorla-msft
  Microsoft Employee
  2 years ago
  Hi JE_test
  
  Thanks for using Microsoft Fabric Community.
  
  Apologies for the inconvenience that you are facing here.
  
  When using Microsoft Fabric Dataflow Gen2 with an on-premises data gateway, you might encounter issues with the dataflow refresh process. The underlying problem occurs when the gateway is unable to connect to the dataflow staging Lakehouse in order to read the data before copying it to the desired data destination. This issue can occur regardless of the type of data destination being used.
  
  For more details, please refer : On-premises data gateway considerations for data destinations in Dataflow Gen2.
  
  If you are using Microsoft Fabric through an on-premises data gateway, be sure to update to the latest version of the gateway. Some errors related to output destinations or queries might be resolved by upgrading the gateway and also this ensures that any updates to Fabric features and known issues are propagated through the gateway.
  
  For details please refer : Currently supported monthly updates to the on-premises data gateways.
  
  We're adding support to cancel ongoing Dataflow Gen2 refreshes from the workspace items view, timeline for the cancel feature, please refer : Cancel refresh support in Dataflow Gen2.
  
  I hope this information helps. Please do let us know if you have any further questions.
  
  Thanks.
  - Element115
    Memorable Member
    2 years ago
    Hold on a sec... are you saying that the following is the path the data takes? This is the sentence that bothers me:
    
    The underlying problem occurs when the gateway is unable to connect to the dataflow staging Lakehouse in order to read the data before copying it to the desired data destination.
    
    1__on-prem DB-->GW-->DefaultStagingLakehouse
    followed by
    2__DefaultStagingLakehouse-->GW-->user lakehouse
    
    Why is the data path instead not like this? Or is it?
    1__on-prem DB-->GW-->DefaultStagingLakehouse
    followed by
    2__DefaultStagingLakehouse -->[ internal Fabric bulk copy mechanism ] --> user lakehouse
miguel
Community Admin
2 years ago
Please do reach out to our support team by raising a support ticket so an engineer can take a look at this

https://support.fabric.microsoft.com/support
- v-cboorla-msft
  Microsoft Employee
  2 years ago
  Hi JE_test
  
  I'm following up to see if you've had a chance to submit a support ticket. If you have, a reference to the ticket number would be greatly appreciated as it would help us to track for more information.
  
  Thanks.
  - Element115
    Memorable Member
    2 years ago
    v-cboorla-msft Do you have an answer to my question requesting clarification re whether or not there is a roundtrip to the on-prem GW?

Forum Discussion

Dataflow refresh started failing today MashupException.Error

26 Replies

Related content

Incremental Refresh on Dataflow sourced from SharePoint

DataFlow Incremental Refresh

Incremental Refresh Dataflow Gen2

Dataflow gen2 - Incremental refresh

Dataflows Failing to Refresh