Unable to delete data workflows gen2 tasks under fabric workspace

I've had this issue too, where downstream artifacts have been deleted, but Gen2 dataflows fail:

Full error message (really would be good to be able to read these messages without having to read the alt-text by hovering over the notification): 'Can't delete the Dataflow Gen2 (CI/CD) 'Load Fact Tables_Archive'. Other items are dependent on this one and may be affected. To see which items are affected items, go to Lineage view.' Executing the API returns a 400:

Pretty clearly a stale platform data issue - have recently deleted downstream objects - but this should be treated as a bug; Fabric shouldn't be claiming there's dependencies that the GUI is showing as deleted.

Interim solution:

Go into the workspace's recycle bin and delete any objects that were downstream of the dataflow. You will then be able to delete the dataflow. Obviously you have to be very sure that what you empty out of the recycle bin won't be needed:

Hello @Santosh Kumar Joshi

A Dataflow Gen2 item normally shouldn't take 7–10 days to delete. Deletion directly from the Fabric workspace using the item's ... → Delete action. Dataflow Gen2 also now has a public API that supports deleting the item directly.

Since you mentioned that deletion initially fails because of lineage/dependencies, first, open the workspace Lineage view and identify both upstream and downstream items connected to that Dataflow Gen2. Fabric's lineage view shows the relationships between items in the workspace and upstream external sources.

If another Fabric item depends on the dataflow, remove that dependency from the dependent item itself rather than only trying to remove what appears in the lineage diagram. In some dependency scenarios, you can't delete an item until you manually remove the dependency.

Also check Monitor hub / Recent runs and make sure the Dataflow Gen2 doesn't have an active refresh. Fabric supports explicitly canceling an in-progress Dataflow Gen2 refresh.

Once there are no active jobs and you've removed the actual dependencies, try deleting the dataflow again from the workspace.

If the UI continues to fail, you can also test the documented Fabric REST API:

DELETE https://api.fabric.microsoft.com/v1/workspaces/{workspaceId}/items/{itemId}
Authorization: Bearer <token>

For Dataflow Gen2, DELETE /v1/workspaces/{workspaceId}/items/{itemId} returns HTTP 200 OK on successful deletion.

Don't repeatedly delete the Dataflow Gen2 staging Lakehouse/Warehouse artifacts as a workaround. DataflowsStaging items are implementation details shared by Dataflows in the workspace, and you shouldn't normally delete them manually.

If the REST DELETE also fails after you remove the dependency, please capture the HTTP status, response body/error code, request ID, workspace ID, item ID, and UTC timestamp. A dependency that appears removed but continues blocking deletion for days could indicate stale Fabric metadata or a service-side cleanup issue, but we need the exact error before concluding that.

Could you share the exact error message shown when you try to delete the Dataflow Gen2 immediately after removing its dependencies? That will help determine whether this is an active dependency, an in-progress operation, a permissions issue, or something that needs Fabric support.

References:

Delete/manage Dataflow Gen2 using Fabric public APIs

Create and delete a Dataflow Gen2

Fabric lineage view

Resolve Fabric dependency errors

Help make this community better for everyone: If this answer helped or resolved your issue, please accept it or upvote it. If not, share more details in a comment so we can continue the discussion and find the right solution. Thank you.