Deadlock error in orchestrator job

Hi Friends,

I had triggered a process in few robots and after an hour or two, 3 of them failed due to the Deadlock error. Please see the screenshot below.


The error says Transactions was deadlocked on lock resources with another process and has been chosen as the deadlock victim.

But the fourth robot processed the transactions successfully. Has anyone ever encountered such an issue?

Hoping for a reply soon.

Apparently, the 4th robot blocked the SQL table you use on that process, and the other 3 robots were not able to use it.

1 Like