Forum Discussion
Advocate IIIDataflow throws "Evaluation failure" after 1-2 minutes only
We are trying to convert power query transformations from pbix to dataflows and multiple queries are throwing "Evaluation failure" error.
It looks like any "foldable" source will throw this error if the remote system is not able to return a resultset within a minute or so.
When using a non-foldable source, or a connector like Odbc.Query, the query is able to show a resultset event after 10-15 minutes refresh.
This is a big issue for us as it prevents us from being able to use any wizard to generate new steps and sometimes, won't even allow us to save the dataflow because it is not able to validate the schema. Since Value.NativeQuery is executing on the remote host, it is considered as "executed remotely", it feels like there is some sort of timeout occuring if the remote host is unable to return a resultset within 60 seconds after it has accepted the remote query.
Any idea why?
Our queries are very simple and are in fact, just a SQL query in a Value.NativeQuery step.
Datasources wher we are experiencing this issue are Google Big Query and SAP HANADB.
GBQ is connected through cloud connector.
SAP HANADB is connected through our on-premise Power BI gateway.
Thanks
Hi FireFighter1017,
If you continue to experience the issue after following the recommended steps mentioned by Akash_Varuna, please consider raising a support ticket for further assistance.
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 for being a part of Microsoft Fabric Community Forum!
15 Replies
- Akash_Varuna
Super User
Hi FireFighter1017 , It might be related to time out limits from foldable sources could you please try these
- Optimize Queries: Simplify SQL queries and use indexing to speed up execution.
- Batch Queries: Fetch smaller datasets using filters or ranges.
- Adjust Gateway Settings: Increase timeout for the on-premises gateway in SAP HANA.
- Try to reduce the Data size during validations
If this post helped please do give a kudos and accept this as a solution
Thanks In Advance
- FireFighter1017
Hi Akash_Varuna ,
The dataset is already shrunk down to ~1200 lines.
I have tried to split all CTEs in the SQL query into separate power query and then merge them (because I need to) and sometimes the separate tables would still return an evaluation failure. Especially the one that has 1200 lines.
From all the testing I have done since yesterday, everything points toward some timeout somewhere down the pipeline between PQO and HANA. Something is causing Power BI to lose connection or drop the request.
The funny thing is that sometimes, I would edit a SQL query in advanced editor, and upon saving my changes, it would run the refresh until it gets to an evaluation failure. I then refresh again and now I get an SQL error.
So it might have something to do with the delay of opening the connection and receiving a status from the remote host.
Gateway settings would probably apply during data refresh as well.
In our case, the same query in a desktop pbix was working.
It is only when PQO is querying the data that it throws the evaluation failure message.
And the error would also come up when querying Google BigQuery, which is not going through our on-premise gateway
v-sgandrathiCommunity Support
Hi FireFighter1017,
If you continue to experience the issue after following the recommended steps mentioned by Akash_Varuna, please consider raising a support ticket for further assistance.
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 for being a part of Microsoft Fabric Community Forum!
I just started getting this same issue on Dataflows where I had not before maybe January or February of this year (2025). The dataflows actually refresh fine, but it makes it difficult to edit a query when I get
in the UI when in "Data View". I do not get this error on the query in the UI when I am in Schema View.
But that isn't helpful when I need to actually see the data.I have tried limiting the number of rows and still get the error. Not sure if anyone has found a solution.
- FireFighter1017
Hi Anonymous ,
Trial and error, that's all I could find to circumvent this problem. We even had to split some SQL queries to optimize execution on the backend and finish the work in Power Query, forcing it to avoid query folding by adding EnableFolding = false parameter in the Value.NativeQuery step or the database connection step you are using.
So far, we have not found how to avoid it other than optimizing the back end by creating compiled tables that are built and filled with the same structure and data we would get with our SQL query, so the query we now have is a simple Select * From ...., which takes only a few second to return data.
That means we can't access live data anymore and have to make sure those tables are refreshed frequently enough for our Power BI artefacts.
- v-sgandrathi
Hi FireFighter1017,
We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?
If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community. If we don’t hear back, we’ll go ahead and close this thread.
Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.
Thank you for your understanding and participation.
- FireFighter1017
I do not have access to open a ticket and I don't know if anybody else in my organisation had open one.
Sorry.
