Forum Discussion
Problems running DataFlow in Fabric
We believe this is an issue specific to My Workspace which occurs in either of the following cases:
1) A query that references another query which has Load enabled
2) A query that outputs to a destination and also has Load enabled
We are investigating the issue and will release a fix as quickly as feasible.
In the interim we believe it should be possible to temporarily work around these issues by using a workspace other than My Workspace.
Thanks.
The issues specific to "My Workspace" are now resolved. For on-premises scenarios, you need the latest version of the Gateway (3000.174.13, published on June 2nd).
Thanks.
I have the same exact issue, but in a workspace that is not My Workspace, so the workaround suggested does not work. Same exact scenario with the organizational logins and the fails are writing due to the token issue described. The pull for our Azure DB works just fine. Are you aware of that this issue is not just in My Workspace?
Also get the same error when pulling data from the Lakehouse with the Gen2 dataflow. I just used copy to successfully load data into the lakehouse I just created and then attempted to use the Lakehouse as the source and got the login error.
Hello Dave_De,
would it be possible to share a screenshot of the failure you are hitting with Request/Session IDs so we can drill down into the issue?
Thanks,
Frank.
I beleive I may have found the issue. If you change the name of the lakehouse even before you have set it as a desitination in the dataflow, then it will fail, but changing it back to the original name helps it go through. Below are the screenshots:
