"CDSALockAcquireError" when attempting to save any Dataflow within a specific Workspace

I believe that is one scenario - yes.   The best workaround I have found for this error, in my scenario (and might work in your scenario) is to assign the connection to a different Gateway.   This will update the configuration in Power Query/BI properly.   I have tried many other workarounds with no success.   It is a known limitation/issue that "Connections" are left hanging around and I believe have a negative impact (this is one of them).

STEPS TO RESOLVE YOUR ISSUE QUICKLY (Full Disclosure, this is a workaround, not a solution which I hope the Power.* Team can ultimately provide):

1) Navigate to Power Query --> Options --> Project --> Data load:   Review the Data Gateway and make note of the gateway used.

2) Navigate to Power Query --> Manage Connections --> and "unlink" all Connections.

3) Once all Connections are removed you will need to provide a new connection.   Pay attention to the connection type used.   We are using OAUTH with Privacy NONE.   Unless there is a reason to, try to eliminate the need for a gateway.   If a connection with a gateway is needed for your scenario, continue with a connection that has a gateway and assign.

4) Go back to Power Query --> Options --> Project --> Data load and assign the connection to a DIFFERENT gateway.   NOTE:  I have NOT had success in assigning to <none> for gateway so you may need to install a 2nd gateway just to use this workaround.

5) Power BI will go through a saving process but go ahead and save the workflow and get out of the dataflow.

3) After Save, go back in to your Dataflow and re-assign the connection to the gateway you want it assigned to <or> in my case, I am removing the requirement for a gateway so I would select <none>.

5) Navigate to Project --> Privacy in the Options window and make sure the "Allow combining data from multiple sources" is selected.   If you do not select this checkbox, you may get blank data or errors when combining multiple datasets from multiple dataflows and it is difficult to track down the root cause.   Click Ok to accept the settings.

6) Save and Close.

7) Refresh.

😎 No error.

9) You can leave as is if it works and the new gateway is ok to use <or> go back through the steps above and reset to None <or> the original gateway.

10) If you have questions while going through the above steps - please respond here and I'll get to you as quick as I can.   I have spent hours on this issue and even logged a ticket with Microsoft that I'm not entirely sure what their next step is.   I asked them to close the ticket (against my better judgement----  we still need a cleaner way to work with Connections and Gateways.   If there are code files we could review / update or scripts we can use to fix this, I would love to know what they are).

Best of luck!

Just had this CDSALockError happen. Turns out there were two other Dataflows refreshing at the same time the dataflow with the issue was attempting to save. Both refreshing dataflows were linked to this dataflow. After canceling the refresh on the other two dataflows, the current dataflow was able to save as expected with no CDSALockError.