The root cause of the previous incident was incorrectly identified.
The actual problem lied in a misconfiguration of the database connection pooling. The database connection limit was exhausted on the client side because of the increased number of locks taken to prevent parallel processing of the same deposits.
Measures are taken to prevent it from happening again.