CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY" trigger failed salesforce

TL;DR

An Apex trigger on the object threw an exception and Salesforce rolled back your write. Get a debug log for the integration user, find the trigger and line that threw, and fix the usual suspects: null dereference, non-bulkified SOQL in a loop, or an unhandled edge in the trigger logic.

Error

[ {
  "message" : "System.DmlException: Insert failed. First exception on row 0 with id a00...; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, LeadTrigger: execution of BeforeInsert caused by: System.NullPointerException: Attempt to de-reference a null object",
  "errorCode" : "CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY"
} ]

Steps

1. Reproduce with a debug log: set a trace flag on the integration user at the finest level, then retry one record. Expected: the log names the trigger and the line number.
2. Read the exception type in the message. NullPointerException means the trigger dereferenced a null (often Trigger.old in an insert context). Expected: you have the bug class before opening code.
3. If the trigger queries inside a loop, that is the bulk failure: one record works, two hundred hit "Too many SOQL queries". Expected: moving the query out of the loop fixes batch loads.
4. Fix defensively in the trigger: null-check lookups, guard Trigger.oldMap access to update/delete contexts, bulkify all queries. Expected: single and bulk writes both pass.
5. If you cannot change the trigger, shape the agent payload to avoid the trigger path (populate the fields the trigger expects). Expected: a documented workaround until the trigger is fixed.

When to use

• Writes fail with CANNOTINSERTUPDATEACTIVATEENTITY naming a trigger.
• Single-record UI saves work but bulk agent loads fail (bulkification bug).
• The failure started after a trigger deployment.

When not to use

• Validation rule errors (FIELDCUSTOMVALIDATION_EXCEPTION).
• Flow errors (those surface as flow fault messages, not trigger exceptions).

Tool compatibility

• Salesforce Apex triggers on any object; debug logs via Setup or the CLI.
• Bulk API and agent write-back jobs that send batches.

Variant phrasings

execution of BeforeInsert caused by

The trigger phase and the root exception follow this phrase.

System.NullPointerException in a trigger

The most common trigger bug; null-check before dereferencing.

Why it happens

Triggers run on every write with no distinction between UI and API. Trigger code written and tested with one record often breaks on bulk payloads or on null fields that interactive users always fill in.

Edge cases

• Trigger.old is null in insert context; code copied from an update trigger crashes on insert.
• Recursive trigger updates can hit the same error on the second pass; guard with a static recursion flag.
• Managed-package triggers cannot be edited; the workaround is payload shaping plus a support case.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_nQhvdh6KcV2Dtsi0GJeGbA