OrgKit / Guides

Salesforce error guides

The errors that stop a data migration at 11pm, explained properly — what the platform is actually objecting to, what does not work, and what does. Written from debugging real orgs, not from paraphrasing the docs.

INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY

You tried to deactivate an Apex trigger and were refused. It is almost never a permissions problem — it is a managed package boundary, and no admin grant will move it.
REQUIRED_FIELD_MISSING on FlowDefinition

Deactivating a Flow through the Tooling API fails naming a missing field. There isn't one — the request body is the wrong shape. Includes the DurableId trap that bites immediately afterwards.
WorkflowRule returns zero rows

Three very different things produce a count of zero, and two of them mean automation is still armed. How to tell them apart before you start a load.
DML operation Insert not allowed on CorsWhitelistEntry

The Apex shortcut for allowlisting an origin works in some orgs and throws in others. Why setup objects behave differently, and the Setup path that always works.

Why these exist

Each of these cost real hours on a real migration before it was understood. The tools on this site came out of the same work — SF Automation Switch for bulk-disabling automation safely, Schema Atlas for documenting a data model, Profile Drift Console for permission drift across orgs.

All free, all browser-based, nothing stored server-side.

See the tools