Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Don't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.

Reply
JeffPtak
Frequent Visitor

Dataflow Editing Issue: Access token expired, resubmit with a new access token

I have several Fabric dataflows that are throwing the error below. Not all of them...only certain ones where the data flow ownership was changed. I was walking a client through the data flow. He took ownership of the data flow so he could navigate the UI. This morninig I logged in to edit one of the data flows that he took ownership of by first re-taking the ownership. Since then I am getting this error. How to get around this?

The data source for the dataflows in question is a Fabric Lakehouse.

I have tried
1) Under Manage Connections, Updating the connection.

2) Logging out of Fabric and clearing my browser cache.

3) I CAN access the lakehouse and view the table contents.

4) My automated Pipeline refresh ran successfully.

 

This is only happening when I try to edit the dataflow.


Downstream service call to url 'https://api.powerbi.com/powerbi/globalservice/v201606/clusterdetails' failed with status code 403. ErrorCode : TokenExpired

Details
Reason = DataSource.Error
Error = [code=TokenExpired,message=Access token has expired, resubmit with a new access token]
ErrorCode = TokenExpired
RequestId = f63718ed-6826-4829-abc4-826c6dd9de05
ErrorMessage = Access token has expired, resubmit with a new access token
1 ACCEPTED SOLUTION
JeffPtak
Frequent Visitor

OK. So I figured this out. The issue was there were several Lakehouse connections in the DataFactory. I was only updating the ones I "thought" I was using. However, apparently, there was one that I never touched (because I didn't create it). That was the one that was causing the issue. Once I update the credentials for that connection, everything started working again.

View solution in original post

6 REPLIES 6
JeffPtak
Frequent Visitor

OK. So I figured this out. The issue was there were several Lakehouse connections in the DataFactory. I was only updating the ones I "thought" I was using. However, apparently, there was one that I never touched (because I didn't create it). That was the one that was causing the issue. Once I update the credentials for that connection, everything started working again.

nilendraFabric
Solution Supplier
Solution Supplier

Hi @JeffPtak 

 

I agree with @miguel , nothing much can be done after the steps you have tried so far.

 

similar case has been discussed in community related to token refresh( it was related to gateway connection)

 

https://community.fabric.microsoft.com/t5/Dataflow/Access-token-has-expired/m-p/3718109

 

Thanks

Thank you. I read through that before I posted. This isn't happening on any of the dataflows where the ownership didn't change hands. So I don't think its a gateway issue.

This is great. We can rule that out. Do share the support case when you have it and my team and I can take it from there

Case 2501260040000898

thank you! 

miguel
Community Admin
Community Admin

Definitely raise a support ticket so an engineer can take a closer look at what could be happening. 
assuming that you take ownership, once you're the owner then you shouldn't be getting token issues with the editing session of your dataflow gen2

Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Prices go up Feb. 11th.

JanFabricDE_carousel

Fabric Monthly Update - January 2025

Explore the power of Python Notebooks in Fabric!

JanFabricDW_carousel

Fabric Monthly Update - January 2025

Unlock the latest Fabric Data Warehouse upgrades!

JanFabricDF_carousel

Fabric Monthly Update - January 2025

Take your data replication to the next level with Fabric's latest updates!