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.
Workaround is to create a new dataflow, rename, then Publish Later. That works. If you rename and Publish Now, it does a Dikembe Mutombo and blocks that shot.
Thanks Martin, you've confirmed my suspicions. We've been seeing the same type of behaviour in our tenant, and it does all seem to stem from the renaming process for dataflows. It's like the dataflow name itself is being used to reference it, instead of an ID behind the scenes, so when you do rename it you need to wait several minutes for everything to sync up again. And if you open up the flow before that sync'ing is done, all hell breaks loose and the flow is, as you say, toast.
Publish Later does seem to bypass the issue, if you wait long enough. Like you I suspect the staging entity behind the scenes is part of the issue.
Very sloppy.