Forum Discussion
Error- Cant connect to the artefact
Hi There,
The metadata in the Fabric Backend was not synced anymore, thats why i got the artefact issue. After 24h, it started to work again. So it was just a matter of waiting.
Super UserKiaZ ,
We’ve run into something very similar before, and the behaviour you’re describing usually happens when the Lakehouse metadata and Delta logs get out of sync with the Fabric backend. Once that happens, connectors (including Dataflows, Excel, Exact Online, etc.) start failing or hanging because they can’t resolve the internal artefact references anymore.
1. Force a rebuild of the Lakehouse metadata
This fixes most “artefact” errors.
In the Lakehouse, go to Files > Tables
Right-click the affected table folder in “Files”
Rename it temporarily (for example, add _old)
Refresh the Lakehouse view
Recreate the table by writing from a notebook or re-running your dataflow
Fabric will rebuild the metadata and table definition from scratch.
2. Clear the corrupted Delta log state
Sometimes adding/dropping columns repeatedly leaves orphaned log entries.
In a notebook:
spark.sql("MSCK REPAIR TABLE lakehouse.tableName")
or for heavy corruption:
spark.read.format("delta").option("ignoreFileNotFound", "true")
This forces Fabric to re-index the table.
3. Regenerate SQL endpoint metadata
This step is important because the SQL endpoint keeps its own cache.
Open the SQL endpoint
Click Manage → Refresh schema
Close and reopen the SQL endpoint completely
This usually clears the “can’t connect to artefact” message.
4. Delete the Lakehouse connection entry under Workspace Settings
This one is easy to miss. The connection object can get stuck pointing to an older internal ID.
Go to Workspace settings → Connections
Remove the connection for the Lakehouse
Re-run your pipeline/dataflow
Fabric will create a fresh binding.
5. For Dataflow Gen2 specifically
If every Dataflow starts failing after a schema change, it often means the runtime binding broke:
Create a brand-new Dataflow Gen2
Add just 1 simple source step
Try refreshing it
If even a brand-new one fails, then the runtime binding is definitely corrupted and a metadata rebuild (steps 1–4) is needed.
6. Exact Online connector workarounds
Exact Online is sensitive to schema changes in the Lakehouse.
GopiKrishna
Ugk161610
First off all, im very grateful for youre advice, i have already deleted the one ''corrupt table'' before ur reply, So does that mean that i need to apply the current spark notebook for all tables in my lakehouse?
Ive refreshed my SQL endpoint schema and renamed my lakehouse tables but without succes...
And how can i use the heavy corrupt notebook code?
And to run my dataflow succesfully, i need to connect my on premise gateway to my connection to run. But whenever i click on manage connections to connect it to my gateway, the screen just freezes on this page. Its the screen where u can apply ur current gateway to ur connection, without applying the gateway i cant refresh the dataflow.
But when i log in to an other admin account it doesnt, so thats weird aswell. Can u please give me some more advice on this? I can really use ur help.
Thankyou