# Salesforce record-locking acceptance checklist

Proposed test contract, not completed test evidence. Run changes only in an approved non-production environment with synthetic fixtures and a bounded test window.

- [ ] Name the business outcome, completion deadline and acceptable unresolved work.
- [ ] Record API family/version, connector settings, concurrency and competing jobs.
- [ ] Retain a sanitized failure sample with timestamps, job IDs and relevant parent keys.
- [ ] Map the suspected contention key and relationship; distinguish evidence from hypothesis.
- [ ] Choose one scheduling, partitioning or transaction change to compare with baseline.
- [ ] Define representative workload and overlap; document differences from production.
- [ ] Retain errors, input identities, successful items, duration, retries and backlog age.
- [ ] Verify required business outcomes separately from write success.
- [ ] Reconcile every input item; do not blindly replay the entire workload.
- [ ] Set bounded retry limits and name the owner of exhausted retries.
- [ ] Record rollback conditions, retained fixtures and the smallest next experiment.
- [ ] Approve a production change separately, based on the actual receipts and limitations.

Acceptance record: environment; start/end/time zone; baseline settings; changed setting; attempted/successful/failed/unresolved; business checks; completion time; oldest outstanding item; exception owners; decision; limitations.
