FAQ: How to resolve "Activity was deadlocked with another user" error in Microsoft Dynamics 365 Business Central


1 comment

  • Marcelo Borges

    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.