Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
I am using a dataflow to query JIRA using REST API's. I moved the query from Desktop to Power BI Service/Dataflow hoping to benefit from using tables from multiple dataflows in one report. One of the queries reaches "Completed" status after 10m 1s consistantly and with the message "Evaluation was cancelled". Is there some time limit associated with how long a data flow query can run?
Solved! Go to Solution.
I created a Support ticket. I got the response I got from Microsoft is as follows:
The authoring limit on Power Query Online is 10 minutes per query. This is the reason for evaluation cancellation error during dataflow creation. We cannot increase or decrease this timeout value. Please note that there is no such timeout value for Power BI Desktop. Reference Document: Power Query Online Usage Limits | Microsoft Docs
You can consider optimizing the query or breaking the query into two to ensure that it takes less than 10 minutes each to execute. If in case, there is no way we can optimize this query. Then the only option left is to use Power BI Desktop instead of Power Query Online (dataflows)."
Hi @Anonymous ,
Thank you for your sharing very much.
I have considered this reason before, but I did not find the relevant documents.
Best regards,
Lionel Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @Anonymous @Anonymous ,
Please create support ticket .
Best regards,
Lionel Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
I created a Support ticket. I got the response I got from Microsoft is as follows:
The authoring limit on Power Query Online is 10 minutes per query. This is the reason for evaluation cancellation error during dataflow creation. We cannot increase or decrease this timeout value. Please note that there is no such timeout value for Power BI Desktop. Reference Document: Power Query Online Usage Limits | Microsoft Docs
You can consider optimizing the query or breaking the query into two to ensure that it takes less than 10 minutes each to execute. If in case, there is no way we can optimize this query. Then the only option left is to use Power BI Desktop instead of Power Query Online (dataflows)."
It isn't just a authoring timeout. There is actually a publishing timeout for GEN2 dataflows that prevents them from being deployed, if they run longer than 10 mins. I think it has the appearance of a bug; and I think they intend to change it in the next one or two years.
This timeout is easy to bypass in semantic models and GEN1 dataflows.
https://learn.microsoft.com/en-us/fabric/data-factory/data-factory-limitations#data-factory-dataflow...
Data Factory Dataflow Gen2 limitations
"After you save/publish your dataflow gen2 we require the validation/publish process to finish within 10 minutes per query. If you exceed this 10 minute limit try to simplify your queries or split your queries in dataflow gen2."
I added a where clause in the sql statement block to narrow the results. Once the M code showed up, I removed the where clause and canceled the evaluation. Closed dataflow and refreshed. Slow but works like a charm.
This worked for me too. Thanks.
This solved my problem!!! Great idea, it's incredible that it works.
well thank you for the answer but now I'd like someone from MS to explain what's the use case for dataflows then.
I'm sorry but this isn't a solution.
It's just acknowledging a limitation of the product.
I have the exact same problem and tried your solution
This is the code
But the evaluation times out after 10 min
Any ideas how to increase the evaluation time ?
Best regards.
I did notice that certain other REST API queries lasting more than 10m went through, so it is not probably a timeout issue. On the other hand, there is no way to figure out what to do to resolve the problem - No diagnostics within Power BI service or details accompanying error message ...
Hi @Anonymous ,
Is it look like this?
And the status is “Completed(10m1s)"?
Maybe the data loading process has timed out.
Try to customize the value of the timeout attribute, for example:
// Timeout is 30 minutes.
Source = Json.Document(Web.Contents("https://[apiservice].com",[RelativePath=thepath],[Timeout=#duration(0,30,0,0)])),
Best regards,
Lionel Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
I meant the first case- time shows 10m 1 s on the status bar shown at the bottom right part of the power query window. The central pane which is supposed to show the result of the query just shows "Evaluation is cancelled"
Hi @Anonymous ,
Do you mean this time?
Or this time?
Does your query return complete data when the status is "Completed"?
Best regards,
Lionel Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 11 | |
| 11 | |
| 9 | |
| 8 | |
| 8 |