Salesforce Reliability and Recovery Patterns

Overview

Make every read, write, job, and event path safe under duplicate, delayed, partial, uncertain, throttled, and unavailable outcomes.

Prerequisites

• Business invariants, sources of truth, operation classes, stable keys, ordering, latency, and recovery objectives
• Current Salesforce API, event, limit, error, job-result, and transaction contracts
• Durable queue and checkpoint stores, quarantine or dead-letter path, reconciliation, backfill, and owners

Tool Discipline

Use Read, Glob, and Grep to inspect approved repository and evidence files, WebFetch to re-check current first-party Salesforce documentation, and Write or Edit only for secretless plans, fixtures, configuration, and redacted receipts.

Current Contract

Salesforce synchronous, composite, bulk, and event surfaces have different transaction, result, retry, ordering, and recovery semantics. CDC can emit gap or overflow events; no transport removes the need for idempotency and reconciliation.