Can't Delete Item

Hi sstipas ,

If you are still having the issue, I wanted to mention that I experienced something very similar this afternoon while deleting a Data Agent. Fabric showed an error message saying the item could not be deleted, but after refreshing the web page, the item had actually been deleted correctly.

It seems that in some cases Fabric may show synchronization or metadata refresh issues in the UI.

Besides that, I would try the following:

1. Refresh the workspace and the Lineage view:Sometimes dependencies are not updated immediately after deleting the Lakehouse or removing notebook connections.

2. Check if the notebook is referenced by any Pipeline, Dataflow, scheduled Job, Deployment Pipeline, or Git/DevOps integration.Even if the Lakehouse connection was removed, the notebook may still be linked from another Fabric item.

3. Open the notebook and check the attached Lakehouse/environment: Make sure there is no default Lakehouse still configured in the notebook settings.

4. Save the notebook after removing the connection: Open the notebook, detach the Lakehouse/environment, save the changes, close it, and then try deleting it again.

5. Check workspace permissions: Make sure you have Admin or Member permissions and not only Contributor, especially if the item was created by another user or through deployment/Git.

6. Review “Manage connections and gateways” or the workspace settings: Verify that there are no remaining connections associated with that notebook.

The imported Python libraries should not normally block deletion. The error seems more related to internal Fabric metadata dependencies than to the code itself.

If the problem continues after refreshing and validating that there are no references from pipelines, schedules, Git, or deployment pipelines, it may be worth opening a Microsoft support ticket, as there could be an orphan dependency remaining in the workspace metadata.

If my comments helped solve your question, it would be great if you could like the two comments and mark it as the accepted solution. It helps others with the same issue and also motivates me to keep contributing.

Thanks a lot, I really appreciate it.

AI was used to ensure clarity of wording