Forum Discussion

Imrans123's avatar
Imrans123
Advocate V
4 years ago

Question about refresh schedule

Hey All, 

 

Was wondering if anyone could help with my queries. I've recently been having failed dataflows and the reason being that I reached my concurrent refresh. The error message states, 

 

Error: Refresh limit exceeded. The up do date limit on concurrent refreshes can be found here: https://docs.microsoft.com/en-us/power-query/power-query-online-limits. Please change the dataflow refresh schedule or upgrade your workspace to Premium capacity and try again. 

 

So when I go the page listed above, I don't see refresh limitation. It only shows me evaluation limitation which I presume is the evaluation that happens once I hit save and change on the dataflow 

 

So I am assuming that 10 concurrent evaluations does not mean 10 dataflows at a time across all my Pro Workspaces.

 

I found another article (https://docs.microsoft.com/en-us/power-bi/transform-model/dataflows/dataflows-features-limitations) where it is stated, 

  • There's no guidance or limits for the optimal number of entities is in a dataflow, however, shared dataflows have a refresh limit of two hours per entity, and three per dataflow. So if you have two entities, and each takes two hours, you shouldn't put them in the same dataflow

What does three per dataflow mean in this scenario? My heaviest dataflow takes 1 hour 20 mins to refresh because of heavy power query transformations. Does it matter if that happens concurrently with other dataflows within the same workspace or different workspace?

 

 

 

Need Help
Show and Tell

1 Reply

  • otravers's avatar
    otravers
    Community Champion
    4 years ago

    Regarding the first point, from the page you linked, you'll see that "during refresh [...] query evaluations return complete results. Data is typically persisted in storage." Meaning, the query evaluations limits listed in that page are not relevant only during authoring but also during refreshes.

     

    Second, "shared dataflows have a refresh limit of two hours per entity, and three per dataflow", i.e. the total refresh time of the entire dataflow should not be more than 3 hours, with any single entity (i.e. table) in it not taking more than 2 of these 3 hours.