Salesforce UNABLE_TO_LOCK_ROW first triage response

When this happens

Use this when only the visible message is known. Do not stop at the screen message; validate the first observable mismatch before any setting is changed first.

Symptom checklist

• UNABLE_TO_LOCK_ROW appears repeatedly in the Salesforce UI or logs.
• profile, permission set, flow, trigger, owner state differs between successful and failed requests.
• The issue appears only after separating data permission issue from Apex/Flow automation issue.
• It often follows deploys, permission changes, configuration edits, or data refreshes.

Likely causes

• UNABLE_TO_LOCK_ROW specifically changes the investigation surface for Salesforce: verify the exact failing object, route, user, and timestamp before applying the broader pattern.
• Two requests write the same logical record at the same time.
• A retry repeats an insert without an idempotency key.
• The unique index or remote branch is correct but the application does not handle conflict paths.
• Transaction lock order differs between workers.
• A batch job reprocesses already imported rows.
• For the first triage case, the first useful clue is the first observable mismatch before any setting is changed.

First 1-minute checks

1. Write down the first failure time, latest change, affected user, path, and object ID.
2. Compare profile, permission set, flow, trigger, owner state for success and failure in the same window.
3. Test the hypothesis: duplicate or lock conflict caused by concurrent writes, missing idempotency, unique keys, transaction order, or remote state drift.
4. Classify this as first triage: the first observable mismatch before any setting is changed.
5. Capture current values before changing configuration.

First evidence

Treat UNABLE_TO_LOCK_ROW as a first triage case. First collect evidence for the first observable mismatch before any setting is changed.

Output examples

Normal output

No matching error appears during the affected request window.

Failing output

The same error appears at the exact request time with the affected path, user, or object.

Output-to-action branches

• Only the visible message is known.
  Collect timestamp, route, request ID, user, and the first backend log line before editing configuration.
• The working and failing outputs differ.
  Act on the differing layer first: For UNABLE_TO_LOCK_ROW, apply the fix only after reproducing the same condition and saving the before/after evidence for this exact code.
• Command output is normal but users still fail.
  Separate browser cache, cookies, permissions, and network location before declaring it fixed.

Do not do this

• Do not change DNS, SSL, cache, and permissions at the same time.
• Do not change multiple layers before identifying the failing layer.
• Do not delete production data, grant broad permissions, or disable security controls as a first response.

Evidence quality

Auto-generated operator draft: includes issue-specific causes, commands, output branches, and unsafe-action warnings. Official-source links and real incident validation are queued for enrichment.

Commands to run first

grep -R "UNABLE_TO_LOCK_ROW" ./logs

sfdx force:user:display

sfdx force:apex:log:list

sfdx force:data:soql:query -q "SELECT Id FROM User LIMIT 1"

grep -R "UNABLE_TO_LOCK_ROW" force-app

grep -R "duplicate\|deadlock\|conflict\|lock\|rejected" ./logs

git fetch --all --prune

git status --short --branch

date -u && grep -R "ERROR\|WARN\|failed" ./logs | tail -n 50

Fix order

1. Record the full UNABLE_TO_LOCK_ROW message, failing URL, user, object ID, and latest change.
2. Collect issue-specific evidence for duplicate or lock conflict caused by concurrent writes, missing idempotency, unique keys, transaction order, or remote state drift.
3. Compare the failing case with a successful case before editing settings.
4. If this is the first triage branch, Collect timestamp, route, request ID, user, and the first backend log line before editing configuration.
5. Re-check with the same command and URL, then record the normal output.

Actions by cause

• For UNABLE_TO_LOCK_ROW, apply the fix only after reproducing the same condition and saving the before/after evidence for this exact code.
• Add an idempotency key or upsert path for repeated writes.
• Use unique constraints intentionally and handle duplicate exceptions.
• Sort lock acquisition order consistently.
• Split batch reprocessing from live writes.
• Fetch remote state before retrying rejected pushes or tags.
• For the first triage branch, Collect timestamp, route, request ID, user, and the first backend log line before editing configuration.

Evidence links

• Salesforce Apex developer guide official
• Salesforce CLI command reference official

Verification metadata

• operator-draft
• official-reference-linked
• 2026-07-23

Update queue

• Review cadence
  weekly-source-review
• Next enrichment
  Add one official-source check and one real output example for Salesforce UNABLE_TO_LOCK_ROW.

Environment-specific checks

• Shared hosting, proxies, VPNs, or CDN layers can change data permission issue from Apex/Flow automation issue results.
• Do not trust only the Salesforce UI; compare command output.
• Japanese hosting panels may show completion before DNS or SSL fully propagates.
• Test from both office and external networks.

Prevent it next time

• Store normal examples for profile, permission set, flow, trigger, owner state.
• Add owner activation, permission sets, validation rules, trigger order to the release checklist.
• Keep recurring errors in the same note format.
• Split alerts by error rate, latency, certificates, disk, and permission changes.

Related notes

• Salesforce INACTIVE_OWNER_OR_USER
• Salesforce INACTIVE_OWNER_OR_USER first triage response
• Salesforce FIELD_CUSTOM_VALIDATION_EXCEPTION first triage response
• Salesforce DUPLICATE_VALUE first triage response
• Salesforce INVALID_CROSS_REFERENCE_KEY first triage response
• Salesforce CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY first triage response
• Salesforce MIXED_DML_OPERATION first triage response
• Salesforce LIMIT_EXCEEDED first triage response