Forum Discussion
Dataflow Gen 1 Refresh Failures starting Last Week
Hi ChristopherKing ,
Thanks for using Microsoft Fabric Community and apologies for the delayed response.
Hope your issue got resolved. If not, please consider the following response.Error #1 : "Insufficient memory (8645)"
Even though you're using Premium capacity, if the dataflow connects through an on-premises gateway, the hardware specs of the gateway can impact performance. It's recommended to have:At least 2 cluster members with 16 GB RAM, or ideally 4 with 32 GB
Good CPU, disk speed, and stable network
This could help reduce memory-related refresh failures, especially if your data size or query complexity has grown.
Solved: Dataflow process error - Microsoft Fabric CommunityError #2 : "Cannot acquire lock for model"
This usually happens when a refresh is interrupted or fails to complete cleanly. The lock often clears after 24 hours, but in rare cases it may persist. Microsoft support can clear it manually if needed.Workaround suggestion:
Reassign the dataflow connection to a different gateway (even temporarily). This helps reset the internal connection mapping and resolve lock errors.
Here is the detailed workaround:Solved: Re: "CDSALockAcquireError" when attempting to save... - Microsoft Fabric Community
If the issue still persists even after the above steps, please raise a support ticket with Microsoft through this link.
Hope this helps. Please reach out for further assistance.
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and a kudos would be appreciated.Thank you.
Hi ChristopherKing ,
Thanks for using Microsoft Fabric Community and apologies for the delayed response.
Hope your issue got resolved. If not, please consider the following response.
Error #1 : "Insufficient memory (8645)"
Even though you're using Premium capacity, if the dataflow connects through an on-premises gateway, the hardware specs of the gateway can impact performance. It's recommended to have:
At least 2 cluster members with 16 GB RAM, or ideally 4 with 32 GB
Good CPU, disk speed, and stable network
This could help reduce memory-related refresh failures, especially if your data size or query complexity has grown.
Solved: Dataflow process error - Microsoft Fabric Community
Error #2 : "Cannot acquire lock for model"
This usually happens when a refresh is interrupted or fails to complete cleanly. The lock often clears after 24 hours, but in rare cases it may persist. Microsoft support can clear it manually if needed.
Workaround suggestion:
Reassign the dataflow connection to a different gateway (even temporarily). This helps reset the internal connection mapping and resolve lock errors.
Here is the detailed workaround:
Solved: Re: "CDSALockAcquireError" when attempting to save... - Microsoft Fabric Community
If the issue still persists even after the above steps, please raise a support ticket with Microsoft through this link.
Hope this helps. Please reach out for further assistance.
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and a kudos would be appreciated.
Thank you.
Error #1 has not occured again since I removed the workspace from the premium capacity and added it back.
For Error #2, I have made some changes to the dataflows that were presenting the issue, and it seems to be corrected, however, I will keep in mind the idea of changing the gateway connection if it occurs again in the future. I use a deployment pipeline, will changing the connection in the Production step of the pipeline cause any issues if i need to deploy changes in the future? I would think not, but I'd just like to verify before I do.
Thank you,
Chris
Hi Chris,
Thanks for the update. Glad to hear Error #1 hasn't reappeared and that the changes you made seem to have helped with Error #2 as well.
Regarding your question about the deployment pipeline:
If you change the connection in the Production stage, it won't break future deployments as long as the connection settings (like name and type) are consistent across stages.If the connection in Production differs from Test/Dev, the deployment won't overwrite the connection itself.
You may need to manually update or reassign the connection in Production after a deployment if anything changes at the source level.
So it's safe to do, just worth keeping track of in case you need to realign connections after deploying updates.
Hope this helps. Please reach out for further assistance.
Would you mind marking any helpful reply or yours as Accepted Solution to help others find the answer quickly who have similar issues and a Kudos would always be appreciated.
Thank you.
