Salesforce UNABLE_TO_LOCK_ROW Error

How to fix it

Try these in order — the most common fix is first.

1. 1. Run the load in serial mode

   Copy steps
   1. In Data Loader enable Use Bulk API and set Serial mode
   2. In integration tools set concurrency to 1
   3. Lower batch size
   Did this fix it? Yes No

2. 2. Sort data by parent

   1. Sort the file by parent ID so children of one parent land in the same batch
   Did this fix it? Yes No

3. 3. Check parent records and schedule

   Copy steps
   1. The locked ID shown may be a parent you did not edit
   2. Stagger batch jobs and run heavy ones off-peak
   3. Move roll-up work to async where possible
   Did this fix it? Yes No

4. 4. Add retry as a safety net

   1. Catch the exception and retry in a Queueable; retry alone does not fix contention
   Did this fix it? Yes No

Symptoms

Data loads, integrations or tests fail with UNABLE_TO_LOCK_ROW: unable to obtain exclusive access to this record.

Why it happens

• Parallel Bulk API batches touching the same parent
• Roll-up summary recalculation on master-detail parents
• Integration concurrency above 1
• Overlapping scheduled jobs and active users

This guide also covers

• unable to lock row salesforce
• salesforce record lock error

The same problem in other apps

All not loading, error messages & connection guides →

• HubSpot Import Errors (HubSpot)
• Pipedrive Import Errors and Skipped Rows (Pipedrive)

Other Salesforce errors

• How to Cancel Salesforce Subscription
• Salesforce REQUEST_LIMIT_EXCEEDED Error
• Salesforce Too Many SOQL Queries: 101 Error
• Salesforce STORAGE_LIMIT_EXCEEDED Error
• Salesforce Einstein Activity Capture Not Syncing
• Salesforce Emails Not Sending
• Salesforce Data Loader INVALID_LOGIN Error
• Salesforce MFA Locked Out: Lost Authenticator