Gen2 Dataflow Refresh Failure - Staging Lakehouse Not Found

[bunny96]

I am unable to successfully refresh a Gen2 Dataflow configured to fetch data from SQL Server and store it in a Lakehouse. The dataflow creation process appears to complete, but when attempting to refresh the dataflow, it consistently fails with a staging lakehouse error

Error Details:

Error Message: "There was a problem refreshing the dataflow: 'Staging lakehouse for dataflow with id ... was not found.'"

Error Code: StagingLakehouseMissingError

Request ID: 00000000-0000-0000-0000-000000000000

Steps Taken:

1. Created a new Gen2 Dataflow
2. Configured data source connection to SQL Server
3. Set destination to Lakehouse
4. Attempted to refresh the dataflow

I would appreciate hearing if others have experienced this problem and successfully resolved it

[v-karpurapud]

Hi @bunny96 

We have not received a response from you regarding the query and were following up to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank You.

[v-karpurapud]

Hi @bunny96 

I wanted to check if you’ve had a chance to review the information provided. If you have any further questions, please let us know. Has your issue been resolved? If not, please share more details so we can assist you further.

Thank You.

[v-karpurapud · Accepted solution]

Hi @bunny96 
Thank you for reaching out to the Microsoft Fabric community forum.

This problem usually occurs when query-level staging is enabled in Dataflow Gen2, rather than being an issue with the SQL Server source or the destination Lakehouse. When staging is enabled, Microsoft Fabric stores intermediate results in an internal staging Lakehouse. If this staging Lakehouse is missing, incorrectly created, or inaccessible due to workspace or permission changes, you may see the error “Staging lakehouse for dataflow was not found” (StagingLakehouseMissingError).

To fix this, open Dataflow Gen2 in the Power Query editor, select the affected source query, and turn off the Enable staging option in the query or managed settings, as @tayloramy suggested. Save the dataflow and try refreshing again. Disabling query-level staging often resolves the issue by preventing Fabric from trying to save intermediate results in the staging Lakehouse.

If the error persists after you disable staging, it means the reference to the internal staging Lakehouse is missing or corrupted. In this case, the recommended solution is to delete and recreate the Dataflow Gen2, making sure a Lakehouse exists in the workspace and you have Contributor or Admin permissions. Recreating the dataflow will restore the required internal staging artifacts and normal refresh behavior.

I hope this helps. If you have more questions, feel free to ask and we’ll be glad to assist further.

Best Regards,

Microsoft Fabric Community Support Team

[tayloramy]

Hi @bunny96, 

Do you have staging enabled on the source? 
Dataflow Gen2 data destinations and managed settings - Microsoft Fabric | Microsoft Learn

If you do, try disabling it.