Forum Discussion
Internal Dataflow Error on Power BI Dataset Refreh
I am posting here about a recent issue that has been popping causing dataset refresh failures. The error message includes an error called an "Internal Dataflow Error" as the cause of the refresh failure.
Example:
| 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":"DataflowInternalError"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.Error","detail":{"type":1,"value":"DataflowInternalError"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataflowInternalError"}},{"code":"Microsoft.Data.Mashup.ValueError.RequestId","detail":{"type":1,"value":"4e91895b-29cf-4fb6-96a2-3d00ff683206"}},{"code":"Microsoft.Data.Mashup.ValueError.RequestUrl","detail":{"type":1,"value":"https://wabi-us-north-central-e-primary-redirect.analysis.windows.net/metadata/v201606/cdsa/dataflows/a747ab73-0c86-4d12-847c-6ad544b51861/contentandcache"}}],"exceptionCulprit":1}}} Table: Dates - Bridge Date Category. |
| Cluster URI: | WABI-US-NORTH-CENTRAL-E-PRIMARY-redirect.analysis.windows.net |
| Activity ID: | 1a9ad50e-e0ba-4347-87ea-66ba5c97b6d2 |
| Request ID: | 1fa05856-84e3-49d2-b27d-9c3255f7cbb3 |
| Time: | 2022-05-25 12:05:18Z |
This error has occurred on exclusively dataflow based datasets, mixed one with SQL Server (and/or MySQL) and dataflows, but not ones lacking dataflows (which makes sense). The first time this occurred was at the end of March 2022 and has been occurring intermittently and without any apparent pattern. I suspect it is linked to a current know issue in Microsoft regarding dataflow refreshes in Premium Capacity: Dataflow Refresh Issues
I had hoped someone else in this community may have experienced this issue and could provide steps toward resolution. I currently have a ticket open with Microsoft Support but they do not know the cause.
Hi, sjrrkb123
I got similar feedback on this issue.
The cause of this issue is due to a known intermittent issue in Premium Gen2 workloads, including dataflows(ICM:297756751)
The issue is also listed in PowerBI Support forum.
https://powerbi.microsoft.com/en-us/support/
Known issue - Long running, failed or stuck dataflow in Premium Gen2
The current advice is to change the workspace to PRO and back to Premium if the problem keeps occurring.
It is recommended to look into reducing the number of entities within a single dataflow .
Best Regards,
Community Support Team _ Eason
6 Replies
Hi, sjrrkb123
I got similar feedback on this issue.
The cause of this issue is due to a known intermittent issue in Premium Gen2 workloads, including dataflows(ICM:297756751)
The issue is also listed in PowerBI Support forum.
https://powerbi.microsoft.com/en-us/support/
Known issue - Long running, failed or stuck dataflow in Premium Gen2
The current advice is to change the workspace to PRO and back to Premium if the problem keeps occurring.
It is recommended to look into reducing the number of entities within a single dataflow .
Best Regards,
Community Support Team _ EasonThis is now happening to us. We were expeirncing random cancellations a few months back. But as of this morning, every single dataflow fails. This issue has been going on since January (per prior support call). Gen 2 has delivered problems, and none of the benefits. We are heavily invested in dataflow usage and I now need to rethink that strategy. The recommneded workarounds are not possibleand way to numerous to keep up with. Just fix it already or put it back that way it was.
m-colbert we have been dealing with this since Gen2 upgrade in December 2021. We have had a ticket open with MSFT from March 2022 regarding this. The only current fix is to change the workspace containing the dataflows from Premium capacity to Pro, wait 10minutes, then switch back to Premium. This sometimes fixes it but not always and is the only known way to address the problem.
According to MSFT, the fixes are coming in two waves, June 30 and July https://powerbi.microsoft.com/en-us/support/
