There was a problem refreshing. Cannot acquire lock for model because it is currently in use

Anonymous  Hopefully it is obvious that it should be Microsoft who is sharing what they know about these bugs, and not customers.  Can you please post your internal wiki and KB and tell us what you learn about this new error (CDSALockAcquireError)?  It appears to be new to Power BI this year.  I never encountered it in the past, and nor do other customers.  My fear is that Microsoft is either aware of the issue and unable/unwilling to fix it... or that they haven't actually worked on this one yet, nor tried to create a repro of their own.

I don't want to spend time fighting some mysterious internal locks in the PBI service which we have no control over.  In this case the issue came up after another series of bugs in the service this past week.

Questions, based on what you find in your internal wiki/KB:

- How often is this error/bug reported by your customers?

- When did customers start encountering it for the first time?  In 2024?

- What is the length of time before the lock (CDSALockAcquireError) is internally released?

- What is the goal of these locks?  Why do they persist long after a dataflow has been cancelled?

- What types of PBI artifacts are affected by this bug?  Is it just gen1 dataflows or other artifacts as well?

- Has Microsoft already deployed any software changes (fixes or workarounds) to mitigate the problem?

Any information would be helpful.  The CSS organization was somewhat familiar but hasn't been encouraged to share any meaningful amount of information yet, other than to tell customers that we must wait 24 hours for the problem to go away on its own.  That is a pretty unacceptable "solution", for most customers.  Admittedly we haven't engaged the PTA/FTE yet on the Microsoft side, and I'm hoping there will be a little more transparency once Microsoft has awareness of our case as well as Mindtree.