Message
"{\"error\":{\"code\":\"Internal_ServerError\",\"message\":\"The activity was deadlocked with another user who was modifying the [X] table. Please retry the activity. CorrelationId:...}
Solution
The error occurs when two transactions are blocking each other. Business Central has a setting called Lock Time-out that is set to 10 seconds by default. You can disable this for long-running processes by calling the Database.LockTimeout(false) function as described in How to solve Table Locking Issues in Business Central.
Note that this article also recommends optimizing the time to complete the transactions. To do this in integrator.io, modify your Microsoft Dynamics 365 Business Central connection settings. Under the Advanced section, set the Concurrency level to 1.
Comments
1 comment
It would be great if we could setup the Concurrency Level per specific steps of the flow, instead of having that setup only on the Connection Level.
I'm testing a flow that works perfectly with no concurrency level (burst mode), but when I needed to add a dimensionSetLines object into my API request, it caused BC to throw the error described on this topic.
My solution was to create a specific connection to be used just at this step of the flow, with concurrency level 1, because for all my other steps, I need burst mode to be activated, otherwise it would take way longer to finish the flow.
Please sign in to leave a comment.