Forum Discussion
Unable to rename Gen2 Dataflow
The case # is 2311030040012138. Looks like whatever the issue was has been resolved. Gen 2 Dataflows we create now don't have issues. Some of the dataflows that were created a couple of weeks ago now though are completely toast. Ownership cannot be switched and the owner can't even open the dataflow. Oh the joys of pre-release software.
One of the things noticed when dataflows miraculously started working again was the appearance of a DataFlowsStagingLakehouse that no one on my team had seen before. Doesn't show up in the workspace but is listed as an option when Lakehouse is selected as a data destination.
Hi MartinMason ,
Following back to check whether you got a chance to create a support ticket?
Incase if you created, please do share the supportcase# here.
The case # is 2311030040012138. Looks like whatever the issue was has been resolved. Gen 2 Dataflows we create now don't have issues. Some of the dataflows that were created a couple of weeks ago now though are completely toast. Ownership cannot be switched and the owner can't even open the dataflow. Oh the joys of pre-release software.
One of the things noticed when dataflows miraculously started working again was the appearance of a DataFlowsStagingLakehouse that no one on my team had seen before. Doesn't show up in the workspace but is listed as an option when Lakehouse is selected as a data destination.
Hey! Please do continue working with the support team on the issues that you've mentioned.
We recently made a change to hide the staging Lakehouse from the workspace list. It was shown before, but based on the feedback that we received it was causing confusion so its being hidden from the workspace list and will be hidden from other experiences in the future. This lakehouse is a system artifact used for evaluations needed by the Dataflow Gen2 engine.
