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.
It's bad. It's really, really bad. Just started happening yesterday and thank god we don't use this feature extensively in our architecture. Because frankly, the motto in our group is Dataflows suck. Not just running a dataflow, it get a dataflow to execute successfully, we have to create a new dataflow, copy all queries to the new dataflow, and then publish. It runs successfully.....once. If you try to refresh that dataflow again without changing a thing, it fails almost immediately. Opening up the newly created dataflow and trying to Publish that dataflow.....fails. Only thing one can do is create a new dataflow copy everything from the previous dataflow and save the new dataflow....which will execute successfully......once. And only once. Can't publish. Can't rename. Can't refresh. Can't take ownership. Somebody broke something badly...at least in our tenet.
Here's what it looks like where I just created Dataflow-6. Dataflow 3 and about four other dataflows are identical. Ran successfully on initial creation and Publish. Right after the initial refresh, tried to kick off again and failed refresh.
Refresh history on Dataflow-6 looks like the following:
Hi MartinMason ,
Apologies for the issue you have been facing.
I would request you to please go ahead with Microsoft support for this. Please raise a support ticket on this link: https://support.fabric.microsoft.com/en-US/support/.
Also once you have opened the support ticket , please do share the supportcase# here.
Thanks.
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.