Dataflow Error: Access token has expired resubmit with a new access token

[gp10]

I'm trying to create a transformation dataflow from a staging dataflow. 
The staging dataflow contains a big volume of data and refreshes fine.
In the transformation dataflow I'm trying to group and aggregate the staging dataflow.
I'm getting this error after an hour or so:

[DM_ErrorDetailNameCode_UnderlyingErrorMessage]=<ccon>Access token has expired resubmit with a new access token</ccon> [DM_ErrorDetailNameCode_UnderlyingHResult]=-2147467259 [Microsoft.Data.Mashup.ValueError.Error]=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" [Microsoft.Data.Mashup.ValueError.Reason]=TokenExpired

How can I solve this?
Thanks.

[gooranga1]

see post

https://community.fabric.microsoft.com/t5/Service/dataflow-invalid-token/m-p/3313722#M199784 

[dribeiro]

@gooranga1 ,thanks, it seems to work.

I'm editing all the connections now...

Very weird to let the dataflow connections unmapped.

I think microsoft needs to improve/fix the management UI, but ok.

[KristofDMi]

Also works here - thanks! 
Had to 'unmap' it in the DG section and then configure the connection below. 

[kevingauv]

We got the same problem since yesterday from a dataflow that use another dataflow as a source.

[vania26]

@gooranga1 Gracias, gracias, gracias!!! Me ha ayudado a resolver mi problema.

[Anonymous]

It's an amazingly ridiculous design that you must assign an owner to a Dataflow and login via OAUTH so that the token expires, requiring an admin to continually re-authenticate to keep these things running. 

It's also amazing that through this thread, no one from Microsoft mentions it or even acts like they want to explain it properly. I can see why, as this having to re-authenticate over time is complete nonsense.

[AlejandroH]

@gooranga1 ,thanks, it seems to work.

[AlejandroH]

@gooranga1 ,thanks, it seems to work.

[Frostwind]

Still getting these errors randomly.

I do believe it happens on On-Premise Gateway when it's under a high load (f.e. if there are few datasets updating simultaneously). Seams like gateway is not always able to refresh tokens in time when it's overloaded.

[otis_pc]

When this issue cropped up for me this month (Nov 2023), it's because when you create a new dataflow and choose to connect to another dataflow, the platform uses the LEGACY connector instead of the current one, and the legacy connector may or may not recognize organizational authentication. When I tried to sign in again, it told me it wouldn't use anonymous credentials (even though I used the organizational account).

Switching to the current connector got rid of the error message.