HI - I have a premium workspace with 5 seperate "Layer 1" ingestion dataflows bringing in data from an Azure data warehouse. No ETL in the dataflows, just pure ingestion.
I have then a single "Layer 2" ETL dataflow in the same workspace that links to all 5 tables, creates "reference" tables of each linked table, marks columns as Key columns, and thats it for now ( ultimately will merge them all, but thats off topic).
The issue is that when I try to run schedule refreshes accross the 5 Layer 1s, one will run, but the others will fail due to Lock error message below. If I delete the Layer 2 dataflow, everything refreshes no problem. If I put the Layer 2 in another workspace, again everything will refresh no problem, however I would prefer not to seperate the full ETL into different workspaces.
Error message :
" There was a problem refreshing your dataflow. xxxx "ErrorMessage":"Cannot acquire lock for model yyyy because it is currently in use"
Is this an expected behaviour ? If so, is there a workaround or proper best practice to setting up ETLs ? If not, what can I do to troubleshoot ? Its definitely the Layer 2 Dataflow causing the issue, I've tested deleting, refreshing, recreating multiple times with same outcome.
Thanks,
Dave
