Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
5 years ago
Solved

Does Dataflow evaluation stop after 10 minutes?

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...
dataflow
  • Anonymous's avatar
    Anonymous
    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)."

     

v-lionel-msft's avatar
v-lionel-msft
Icon for Community Support rankCommunity 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's avatar
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's avatar
    Anonymous
    Not applicable
    4 years ago

    I'm sorry but this isn't a solution.

    It's just acknowledging a limitation of the product.

  • Anonymous's avatar
    Anonymous
    Not applicable
    4 years ago

    well thank you for the answer but now I'd like someone from MS to explain what's the use case for dataflows then.

  • Smaccallum's avatar
    Smaccallum
    New Member
    3 years ago

    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.

    • Anonymous's avatar
      Anonymous
      Not applicable
      2 years ago

      This solved my problem!!! Great idea, it's incredible that it works.

    • reachsarfaraz's avatar
      reachsarfaraz
      New Member
      8 months ago

      This worked for me too. Thanks.

  • dbeavon3's avatar
    dbeavon3
    Icon for Memorable Member rankMemorable Member
    1 year ago

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