Multiple processes are trying to update the same record at the same time.

Problem Explanation

Salesforce locks records during updates. When Flows, triggers, or integrations attempt concurrent updates, the database prevents conflicts by throwing a row lock error.

Root Cause(s)

1. Parallel Flow interviews updating same record

2. Batch or integration running simultaneously

3. Parent–child record updates in loops

Step-by-Step Solution

1. Reduce record updates inside loops

2. Move non-critical updates to scheduled paths

3. Ensure parent records are updated once per transaction

4. If using Apex, retry logic with Queueable Apex

Edge Cases & Variations

1. More common in high-volume orgs

2. Record-triggered Flows on parent objects amplify locking

Common Mistakes to Avoid

1. Updating the same record repeatedly

2. Ignoring scheduled paths for heavy updates