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

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Token has expired error

I'm randomly getting errors all over the place about a token that has expired when trying to refresh a dataset that is connected to a Dataflow.

I noticed that this only happens when I connect to the Dataflow via the "= PowerPlatform.Dataflows(null)" connector.

When I connect through the Dataflow (Legacy) connector, everything works fine.

 

Please help as this is driving me crazy.

 

{"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"Access token has expired, resubmit with a new access token"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.Error","detail":{"type":1,"value":"error \"Microsoft.Mashup.Engine1.Runtime.ValueException: [Expression.Error] The field 'pbi.error' of the record wasn't found.#(cr)#(lf) at Microsoft.Mashup.Engine1.Language.ValueCreator.CreateValueForThrow(IThrowExpression throwExpr)#(cr)#(lf) at Microsoft.Mashup.Engine1.Language.ValueCreator.<>c__DisplayClass23_0.<CreateValueForRecord>b__0(Int32 index)#(cr)#(lf) at Microsoft.Mashup.Engine1.Runtime.RecordValue.DemandRecordValue.get_Item(Int32 index)#(cr)#(lf) at Microsoft.Data.Mashup.ProviderCommon.MashupResource.TryGetValue(Func`1 getValue, IValue& value, String& errorMessage)#(cr)#(lf)Record\""}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"TokenExpired"}},{"code":"Microsoft.Data.Mashup.ValueError.RequestId","detail":{"type":1,"value":"41a4cf24-1f56-4454-8a94-36dbc97ffb7a"}},{"code":"Microsoft.Data.Mashup.ValueError.RequestUrl","detail":{"type":1,"value":"https://api.powerbi.com/powerbi/globalservice/v201606/clusterdetails"}}],"exceptionCulprit":1}}} Table: DimDate.

Status: Accepted

Hi @Noeleke1301 ,

Configurable token lifetimes - Microsoft Entra | Microsoft Learn

"The default lifetime of an access token is variable. When issued, an access token's default lifetime is assigned a random value ranging between 60-90 minutes (75 minutes on average)."

As mentioned in the above doc, the token lifetime is not constant. So if luckily the token lifetime is closer to 90mins, the refresh will succeed because the total refresh time is still below 90mins.

 

Best regards,
Community Support Team_Binbin Yu

Comments
v-yetao1-msft
Community Support
Status changed to: Accepted

Hi @Noeleke1301 

It’s a known issue . The engineers are actively working on this issue and I will come back with an update if there is any progress.

 

Best Regards,
Community Support Team _ Ailsa Tao

Carissalindgren
Regular Visitor

Is there an update on this? It is becoming a huge problem with multiple reports connected to Dataflows failing to refresh. I used to be able to connect to legacy Dataflows and it worked but this morning Legacy and Power Platform Dataflows are not working to connect a report to and be able to refresh within the service. 

v-binbinyu-msft
Community Support
Status changed to: Accepted

Hi @Noeleke1301 ,

Configurable token lifetimes - Microsoft Entra | Microsoft Learn

"The default lifetime of an access token is variable. When issued, an access token's default lifetime is assigned a random value ranging between 60-90 minutes (75 minutes on average)."

As mentioned in the above doc, the token lifetime is not constant. So if luckily the token lifetime is closer to 90mins, the refresh will succeed because the total refresh time is still below 90mins.

 

Best regards,
Community Support Team_Binbin Yu

Noeleke1301
Helper III

@v-binbinyu-msft Are you implying that my refresh is taking longer than 60 mins? It's a calculated Date table that has never taken longer than 31 seconds to refresh. I checked the refresh history of the last couple months.