Forum Discussion
can't load a file from lakehouse using Data Flow Gen2
I try to load a csv file using dataflow gen2. I have removed any connection in the current project or global permission table. I was guided to create a data connection, and I can select the lakehouse, but couldn't open the lakehouse. Below is the error message.
The user I'm using is the workspace admin, hence I should have access to all the Lakehouses in this workspace.
I remember I have encountered similar problems before, and the problem is fixed by itself. Maybe there is a delay with Fabric connection update.
Hi jean0304 ,
Thank you for reaching out to the Microsoft Fabric Community Forum.
This behavior is not caused by missing Lakehouse permissions. Even though you are a Workspace Admin, Dataflow Gen2 uses Fabric data connections and access tokens that can take time to synchronize, especially if connections or permissions were recently modified or recreated.
In this case, the Lakehouse may appear selectable but cannot be opened or browsed from Dataflow Gen2. This is a known intermittent Fabric behavior and is typically resolved once backend synchronization completes.
Recommended actions to be taken:
-
Sign out and sign back in to Fabric to refresh the token.
-
Try again after some time to allow connection propagation.
-
Open Fabric in a new InPrivate/Incognito browser session.
-
If needed, recreate the Dataflow Gen2 after the sync completes.
Since you’ve seen this resolve on its own previously, this aligns with a Fabric connection sync delay rather than a configuration issue.
If the issue persists after several hours, please share the exact error text and confirm whether it occurs across multiple Lakehouses.
-
3 Replies
Hi jean0304 ,
Thank you for reaching out to the Microsoft Fabric Community Forum.
This behavior is not caused by missing Lakehouse permissions. Even though you are a Workspace Admin, Dataflow Gen2 uses Fabric data connections and access tokens that can take time to synchronize, especially if connections or permissions were recently modified or recreated.
In this case, the Lakehouse may appear selectable but cannot be opened or browsed from Dataflow Gen2. This is a known intermittent Fabric behavior and is typically resolved once backend synchronization completes.
Recommended actions to be taken:
-
Sign out and sign back in to Fabric to refresh the token.
-
Try again after some time to allow connection propagation.
-
Open Fabric in a new InPrivate/Incognito browser session.
-
If needed, recreate the Dataflow Gen2 after the sync completes.
Since you’ve seen this resolve on its own previously, this aligns with a Fabric connection sync delay rather than a configuration issue.
If the issue persists after several hours, please share the exact error text and confirm whether it occurs across multiple Lakehouses.
Sign out and sign in doesn't solve the problem. I was able to update the connector on PB service the next day. So the learning is be careful with connection creation because the refreshing of connector is slow on PB service.
-
Hi jean0304 ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
Thank you.
