Forum Discussion
Can't save dataflow, cannot acquire lock for model
- 6 years ago
Hmmm I cancelled out, waited a few minutes, and went to make my changes again--however the changes are there.
So the save went through even with the model lock error...I wonder if it was trying to save twice behind the scenes? The first save went through and the second failed because of the first pending, throwing the message?
- 6 years ago
This is what I've observed.
I have a few dataflows at work here.
For each entity, I have:
- Ingest
- Cleanse
- Final
So I have
- Customers_1-Ingest
- Customers_2-Cleanse
- Customers_3-Final
- Orders_1-Ingest
- Orders_2-Cleanse
- Orders_3-Final
Each previous dataflow is a linked entity in the following one ("Customers_1-Ingest" is a linked entity in "Customers_2-Cleanse"). So refreshing the "1-Ingest" dataflows will refresh the downstream dataflows.
This also puts a lock on them.
All my "Final" queries are added as linked entities in "For Consumption_Customers and Orders". Since they're linked, this dataflow gets locked when something upstream is refreshing.
What I've noticed is:
- I can't refresh more than one "1-Ingest" at a time, because the first one puts on a lock on "For Consumption" so the second "1-Ingest" I try to run is unable to get the lock and fails with "MWC client failed with user or caller error".
Hi jeffshieldsdev ,
I saw you can do "save" action currently. Is your problem solved? If it is solved, you can accept your own answer.