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?

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 DocsYou 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)."

Does Dataflow evaluation stop after 10 minutes?

14 Replies

Anonymous
Not applicable
5 years ago
Hi v-lionel-msft

I have the exact same problem and tried your solution

This is the code

Source = Csv.Document(Web.Contents(Url, [Headers=[Authorization=AuthToken],Query=[start=StartDate,type="completion"], Timeout=#duration(0,30,0,0)]),
// I tried duration in all variation also #duration(0,0,30,0)])
[Delimiter=",", Columns=29, Encoding=65001, QuoteStyle=QuoteStyle.Csv]),

But the evaluation times out after 10 min

Any ideas how to increase the evaluation time ?

Best regards.
- Anonymous
  Not applicable
  5 years ago
  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 ...
v-lionel-msft
Community Support
5 years ago
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.
Anonymous
Not applicable
5 years ago
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"
v-lionel-msft
Community Support
5 years ago
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.
v-lionel-msft
Community Support
5 years ago
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.
- Anonymous
  Not applicable
  5 years ago
  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)."
  - Anonymous
    Not applicable
    4 years ago
    I'm sorry but this isn't a solution.
    It's just acknowledging a limitation of the product.
v-lionel-msft
Community Support
5 years ago
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.