Forum Discussion
There was a problem refreshing. Cannot acquire lock for model because it is currently in use
My dataflows are acting more buggy than normal. I've been trying to refresh a stand-alone dataflow all day long. It always says: There was a problem refreshing your dataflow. {"RootActivityI...
According to a support ticket I created, this painful issue is actually by design.
Microsoft appears to be placing some sort of internal "locks" on dataflow components when a concurrency/synchronization issue takes place. The locks will prevent your environment from working properly for at least a day, and causes a situation to go from bad to worse.
According to the Microsoft engineer, I'm told that:
"A lock was automatically placed on the dataflow. This lock should be removed after 24 hours automatically, and the refreshes show work as usual."
.. I'm still trying to find some public documentation, since none of this makes any sense.