Refresh error Gen 2 CI/CD: Mashup Exception Data Source Error

[NovaBI]

Hello,

since today, all Dataflows Gen 2 that do not use a SQL Endpoint failed.

If i go through the tables that are ingested into the flow, everything is shown correctly.

I already tried to disable staging, but that does not help. There is a lakehouse, at least this is stated:

Error Code: Mashup Exception Data Source Error, Error Details: Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: Failed to insert a table., InnerException: Unable to create a table on the Lakehouse SQL catalog

The error message is much longer, I wont post it for clarity right now, can do if needed.

Any idea why this can happen?

[v-pnaroju-msft]

Hi NovaBI,

We are following up to see if what we shared solved your issue. If you need more support, please reach out to the Microsoft Fabric community.

Thank you.

[v-pnaroju-msft]

Thankyou, @Vinodh247 for your response.

Hi NovaBI,

We appreciate your inquiry through the Microsoft Fabric Community Forum.

We would like to inquire whether have you got the chance to check the solution provided by @Vinodh247to resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.

Thank you.

[Vinodh247]

You do not need table IDs. Delete tables by name.

Fastest options:

• Lakehouse UI: Open lakehouse -> Tables -> select table -> Delete (recommended).

• SQL endpoint: DROP TABLE IF EXISTS dbo.table_name; 

• Spark (if catalog is broken):spark.sql("DROP TABLE IF EXISTS table_name")

After deletion, rerun the Dataflow Gen2 so Fabric recreates the table and fixes the catalog.

[Vinodh247]

This is almost certainly a Fabric serviceside regression or backend change affecting DataflowsGen2 lakehouse table creation, not your data or mashup logic. The key signal is “Unable to create a table on the Lakehouse SQL catalog” while previews work and SQL Endpoint based flows succeed. That points to a failure in the lakehouse metadata or SQL catalog sync layer that Gen2 uses during refresh, especially when staging is involved. This has happened before during Fabric backend updates. Your mitigation options are limited: retry later, switch temporarily to SQL Endpoint ingestion where possible, or recreate the target tables in the lakehouse to force metadata realignment. If this started today across multiple flows, raise a Microsoft support ticket immediately and check the Fabric Service Health dashboard; do not spend time refactoring mashups, it will not help.

[NovaBI]

@Vinodh247 ,

thanks for the imput. How do I delete the tables in the lakehouse?

Do I need to identify them via Id?