Forum Discussion
Dataflow Gen2 (CI/CD) Non-deterministic failure - Unknown evaluation error code: 104100
Hi,
A colleague of mine has developed a Gen2 (CI/CD) dataflow and has shown that they have got a refresh failure after a while which has not been traced and has gone away after a manual on-demand refresh and resumption of the schedule. Although the failure is from the same step in the dataflow each time it cannot be reproduced except when the dataflow is scheduled and from what I can see from the refresh history the dataflow only has had Unknown evaluation error code: 104100
On the assumption this is not a data-issue has anyone similar behaviour for a dataflow?
Hi royclack ,
The error, 104100 is a generic Power BI Dataflow error that indicates an "Unknown evaluation error."
This generally means the Power Query (M) engine encountered something during runtime that prevented evaluation—but it couldn’t map it to a specific root cause. These errors often disappear on manual refresh, making them hard to trace.You can try to troubleshoot this by following these steps-
1. Schedule dataflows to run at different times to avoid capacity issues.
2. Use the “View Native Query” tool in Power Query Editor to ensure folding is consistent and valid. Test all data sources independently for timeout.
3. After deploying via CI/CD, do a one-time manual refresh before scheduling it.If you are still not able to resolve the issue, consider raising a support ticket.
To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
If this post helps, please give us Kudos and consider marking it Accept as solution to assist other members in finding it more easily.
Thank You!
7 Replies
Hi royclack ,
The error, 104100 is a generic Power BI Dataflow error that indicates an "Unknown evaluation error."
This generally means the Power Query (M) engine encountered something during runtime that prevented evaluation—but it couldn’t map it to a specific root cause. These errors often disappear on manual refresh, making them hard to trace.You can try to troubleshoot this by following these steps-
1. Schedule dataflows to run at different times to avoid capacity issues.
2. Use the “View Native Query” tool in Power Query Editor to ensure folding is consistent and valid. Test all data sources independently for timeout.
3. After deploying via CI/CD, do a one-time manual refresh before scheduling it.If you are still not able to resolve the issue, consider raising a support ticket.
To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
If this post helps, please give us Kudos and consider marking it Accept as solution to assist other members in finding it more easily.
Thank You!royclack Could you check this thread post it has similar error
https://community.fabric.microsoft.com/t5/Dataflow/DataFlow-Gen2-104100-Couldn-t-refresh-the-entity-because-of-an/m-p/3686873Akash_Varuna There's no reference to that error and no datagateway usage
