How to Fix UNABLE_TO_LOCK_ROW Error in Salesforce?

The Salesforce UNABLE_TO_LOCK_ROW error occurs when Salesforce is unable to obtain an exclusive lock on a record during an update operation. To ensure consistency, Salesforce automatically locks a record when it is being updated.

If any other user, automation or integration tries to modify the same record at the same time, Salesforce throws the UNABLE_TO_LOCK_ROW error to avoid conflicting updates.

The error typically appears as:

This is commonly caused by concurrent processing. For your reference, here are the most common reasons of UNABLE_TO_LOCK_ROW error:

If multiple batch jobs attempt to write to the same parent or related records, Salesforce can’t lock and throws UNABLE_TO_LOCK_ROW

External systems syncing data in real time can attempt to update the same record as internal automation. This overlap often triggers the UNABLE_TO_LOCK_ROW error

In concurrent transactions, if multiple Flow or Apex triggers try to write to the same record, you may experience an UNABLE_TO_LOCK_ROW error.

Large data imports by Data loader or Bulk API has higher record contention risk that can lead to UNABLE_TO_LOCK_ROW when related objects are involved.

High-volume transaction organisations are more susceptible to UNABLE_TO_LOCK_ROW due to concurrent updates.

UNABLE_TO_LOCK_ROW error is common in enterprise environments with heavy automation.

Solve UNABLE_TO_LOCK_ROW, reduce record contention and improve automation? Here are strategies to help you.

Avoid running multiple batch jobs or integrations simultaneously on the same object.

Switching from parallel mode to single-threaded mode mitigates the locking conflict that results in UNABLE_TO_LOCK_ROW.

Using smaller batches lessens the chances of record contention and fewer UNABLE_TO_LOCK_ROW.

Many integrations can retry failed operations automatically. A retry mechanism often resolves temporary UNABLE_TO_LOCK_ROW errors.

Review Flows, Process Builders, and Triggers that may be updating the same records.

The UNABLE_TO_LOCK_ROW error is built into Salesforce to help protect your data. We understand that you can get interrupted integrations and automation, but with the right architecture, proper serial processing, and well-optimised batch execution, this can be largely minimised.Understanding the root cause of UNABLE_TO_LOCK_ROW allows admins and developers to build more scalable and reliable Salesforce solutions.