Forum Discussion
Data Flow refresh - parallel or separately
- 7 years ago
Anonymous ,
Currently there's no such kind of doc which can clarify the working details about dataflow entity refresh. But it seems to more related to Azure Lake Storage. I would suggest you to post this question to azure forum to achieve more help.
Community Support Team _ Jimmy Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Any update on this issue? I am using Invoke After as a work around as I have multiple tables using the same API source and I'm hitting the quota limit. But it takes a long time to refresh as I give exessive breathing room between queries since sometimes the API works slow..
I have the same issue which causes an error when refreshing my dataflow "Parallel API request not permitted".
Any help would be appreciated.
- PawelWrona2 years agoResolver II
You can download the refresh history form Dataflows:
Inside you will find StartTime and EndTime for each entity
As you can see even on my example, some of the are overlapping, this might cause an issue. In this case, probably it's better to split entities to individual dataflows and run them in sequence, if this is your data source limitation.
Also, if you have issue with too frequent API Calls according to your data source rules, you may have a look at the great post from Chris Webb:
Chris Webb's BI Blog: Using Function.InvokeAfter() In Power Query (crossjoin.co.uk)