ASSIGN ORDER GENERAL LEDGER CODES Action is causing DB deadlocks

Hi!

It appears that this action is trying to update Order Release Line's update time stamp and Order Release at the same time generating database deadlock.

We tried to use this action on an agent that fires when order release is created, we tried it on a shipment Secure Resources Accepted status change.  Now we are running a recurring process that looks for Order Releases without Buy Side GL and throws a custom event.  An agent is listening for that event and the only thing it does is to perform that action.  The Agent's Error Handler sends an email when it fails, so I get emails while the GL code actually is getting assigned.  Our DBAs are seeing deadlocks in the DB during this process.