Report dataset refresh failure when using dataflow as data source

[PBI_AAA]

Starting 7/11/2023 17:00 CST all reports using dataflows as a datasource are failing to refresh in the service.  All give a similar error of "Access token has expired", and I've included one example below.  All reports refresh in desktop application, this is only occurring in the service.

Data source error: {"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":"284a2330-13e8-481e-a498-8284078e5699"}},{"code":"Microsoft.Data.Mashup.ValueError.RequestUrl","detail":{"type":1,"value":"https://api.powerbi.com/powerbi/globalservice/v201606/clusterdetails"}}],"exceptionCulprit":1}}} Table: Shipper DM.
Cluster URI: WABI-US-NORTH-CENTRAL-H-PRIMARY-redirect.analysis.windows.net
Activity ID: d57790b8-e591-4464-a4f2-a5d00e862ae3
Request ID: f033803e-eaad-413b-94b7-aa2366b938dd
Time: 2023-07-12 09:03:35Z

[Anonymous]

Hi @PBI_AAA 

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

[Anonymous]

Since midnight we are also experiencing this issue. A few dataflows and reports connected to them failed with the access token 'pbi.error' not found message.

Furthermore, none of the dataflows can be used in service but they work locally (in the service, when expanding the workspace folder, nothing appears as it is not detecting any available premium workspaces):

To clarify, the issue is in any dataflow or dataset that has a dataflow as a datasource @Anonymous 

[fh2810]

Hi, @Anonymous , is there any update on this. We have the same issue since 12/07/2023 

[AK1234]

Hi @v-yetao1-msft  i am having the same issue since 12/07/2023. We raised a ticket with microsoft and they are having no luck.  They didn't mention this issue whilst investigating, how do you know it is a known issue?

[egnvictorfarias]

  Hi, I managed to solve it! 

Despite appearing online, it wasn't working: the problem started after I was 'forced' to change my office365 password, I edited the 2 Gateways and confirmed my credentials.

I just clicked edit and confirmed the credentials. Then I tried refreshing the dataset and it worked.

This must be done for each gateway that has credentials (file/folder/etc)