Salesforce Integration Incident Response

Overview

Restore business invariants safely by separating Salesforce platform state, customer org state, application behavior, data correctness, and event delivery.

Prerequisites

• Incident commander, severity model, affected environments and workloads, communications, and evidence channel
• Current deployment, org identity, app and principal, API, limits, jobs, events, data, and reconciliation contracts
• Pre-approved containment, failover, deferral, rollback, credential revocation, and vendor escalation procedures

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 Status reports platform incidents, while org-specific authorization, limits, metadata, automation, jobs, events, and data can fail independently. A green platform status does not prove an integration or business invariant is healthy.