Dataflow chain refresh error - lock model

[Anonymous]

I have 3 Dataflows created which basically brings tables from 3 different sources.

Then I tried to create a Transformation Dataflow in which I am using all the linked tables coming from earlier Dataflows.

While I try to schedule these 3 Dataflows at the same time say for example DF1, DF2, DF3 at 8:00 it's getting failed due to below error.

"Cannot acquire lock for model xxxxxx because it is currently in use."

Does this mean I can't refresh all the three DF's at the same time? I don't want to wait for 30 mins interval for second DF to refresh and consecutively another 30 mins for next.

Can I know why is this happening please?

[alexgor87]

I had the same error with the linked dataflows: "Cannot acquire lock for model <...> because it is currently in use". My scenario is the following: DF1->DF2, DF1->DF3. All DFs are in the same workspace.

My observations:
1. If the DF1, DF2, DF3 have a refresh scheduled on the same time, then DF1 returns an error.
2. If the DF1 is scheduled to 30 minutes before DF2 and DF3, then it runs well.
Yes, the DF1 refresh triggeres an automatic refresh of the destination DFs, and DF2 and DF3 are refreshing twice, but there are no errors in this scenario.
Hope this will help.

[Anonymous]

The Sources I am using are MYSQL, SQL On Premesis, Sharepoint. Only one out these will be successful as the other will throw the below error.

Anything to do with gateway settings? This is strange.

The Transformation Dataflow will auto refresh soon after actual DF1, DF2, DF3 starts refresh as I am using linked Entities from them as said above. Thanks for your help

[v-rzhou-msft]

Hi @Anonymous 

I found some blogs about refresh dataflow, I hope they could help you.

Blog1: Dataflows in Power BI: Overview Part 5 – Data Refresh

Blog2: Dataflows - Refresh Dataflow

Best Regards,

Rico Zhou

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.