Salesforce Integration Error Triage

Overview

Classify the failed layer, preserve request context, and test one evidence-backed hypothesis before proposing a bounded, reversible correction.

Prerequisites

• Timestamp, environment, principal, operation, request or job ID, and redacted response
• Expected API version, object and field contract, permissions, limits, automation, and recent changes
• Incident, application, Salesforce platform, security, and data 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 exposes documented HTTP and API errors, but the same symptom can originate from OAuth, permissions, sharing, schema, validation, automation, locks, limits, asynchronous processing, or event state. Diagnose the returned evidence in org context.