Salesforce response notes

mediumSalesforce5 min read

Salesforce INACTIVE_OWNER_OR_USER

A practical cause and fix order for INACTIVE_OWNER_OR_USER errors while operating Salesforce.

Salesforce INACTIVE_OWNER_OR_USER first triage response

A Salesforce first triage note for INACTIVE_OWNER_OR_USER: authorization failure caused by missing role, stale owner, key mismatch, inherited deny, WAF policy, or object-level permission. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce FIELD_CUSTOM_VALIDATION_EXCEPTION first triage response

A Salesforce first triage note for FIELD_CUSTOM_VALIDATION_EXCEPTION: Salesforce failure caused by validation rule, governor limit, field-level security, API name drift, or automation order. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce DUPLICATE_VALUE first triage response

A Salesforce first triage note for DUPLICATE_VALUE: duplicate or lock conflict caused by concurrent writes, missing idempotency, unique keys, transaction order, or remote state drift. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce INVALID_CROSS_REFERENCE_KEY first triage response

A Salesforce first triage note for INVALID_CROSS_REFERENCE_KEY: authorization failure caused by missing role, stale owner, key mismatch, inherited deny, WAF policy, or object-level permission. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY first triage response

A Salesforce first triage note for CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY: DNS resolution failure caused by missing records, wrong authority, stale TTL, policy records, or service target mismatch. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce MIXED_DML_OPERATION first triage response

A Salesforce first triage note for MIXED_DML_OPERATION: duplicate or lock conflict caused by concurrent writes, missing idempotency, unique keys, transaction order, or remote state drift. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce UNABLE_TO_LOCK_ROW first triage response

A Salesforce first triage note for UNABLE_TO_LOCK_ROW: duplicate or lock conflict caused by concurrent writes, missing idempotency, unique keys, transaction order, or remote state drift. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce LIMIT_EXCEEDED first triage response

A Salesforce first triage note for LIMIT_EXCEEDED: Salesforce failure caused by validation rule, governor limit, field-level security, API name drift, or automation order. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce INVALID_FIELD first triage response

A Salesforce first triage note for INVALID_FIELD: Salesforce failure caused by validation rule, governor limit, field-level security, API name drift, or automation order. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce Apex heap first triage response

A Salesforce first triage note for Apex heap: application runtime failure caused by exception, parser error, framework wiring, database adapter, automation trigger, or recursive call. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce INACTIVE_OWNER_OR_USER post-release regression response

A Salesforce post-release regression note for INACTIVE_OWNER_OR_USER: authorization failure caused by missing role, stale owner, key mismatch, inherited deny, WAF policy, or object-level permission. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce FIELD_CUSTOM_VALIDATION_EXCEPTION post-release regression response

A Salesforce post-release regression note for FIELD_CUSTOM_VALIDATION_EXCEPTION: Salesforce failure caused by validation rule, governor limit, field-level security, API name drift, or automation order. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce DUPLICATE_VALUE post-release regression response

A Salesforce post-release regression note for DUPLICATE_VALUE: duplicate or lock conflict caused by concurrent writes, missing idempotency, unique keys, transaction order, or remote state drift. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce INVALID_CROSS_REFERENCE_KEY post-release regression response

A Salesforce post-release regression note for INVALID_CROSS_REFERENCE_KEY: authorization failure caused by missing role, stale owner, key mismatch, inherited deny, WAF policy, or object-level permission. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY post-release regression response

A Salesforce post-release regression note for CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY: DNS resolution failure caused by missing records, wrong authority, stale TTL, policy records, or service target mismatch. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce MIXED_DML_OPERATION post-release regression response

A Salesforce post-release regression note for MIXED_DML_OPERATION: duplicate or lock conflict caused by concurrent writes, missing idempotency, unique keys, transaction order, or remote state drift. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce UNABLE_TO_LOCK_ROW post-release regression response

A Salesforce post-release regression note for UNABLE_TO_LOCK_ROW: duplicate or lock conflict caused by concurrent writes, missing idempotency, unique keys, transaction order, or remote state drift. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce LIMIT_EXCEEDED post-release regression response

A Salesforce post-release regression note for LIMIT_EXCEEDED: Salesforce failure caused by validation rule, governor limit, field-level security, API name drift, or automation order. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce INVALID_FIELD post-release regression response

A Salesforce post-release regression note for INVALID_FIELD: Salesforce failure caused by validation rule, governor limit, field-level security, API name drift, or automation order. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce Apex heap post-release regression response

A Salesforce post-release regression note for Apex heap: application runtime failure caused by exception, parser error, framework wiring, database adapter, automation trigger, or recursive call. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce INACTIVE_OWNER_OR_USER affected user or permission response

A Salesforce affected user or permission note for INACTIVE_OWNER_OR_USER: authorization failure caused by missing role, stale owner, key mismatch, inherited deny, WAF policy, or object-level permission. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce FIELD_CUSTOM_VALIDATION_EXCEPTION affected user or permission response

A Salesforce affected user or permission note for FIELD_CUSTOM_VALIDATION_EXCEPTION: Salesforce failure caused by validation rule, governor limit, field-level security, API name drift, or automation order. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce DUPLICATE_VALUE affected user or permission response

A Salesforce affected user or permission note for DUPLICATE_VALUE: duplicate or lock conflict caused by concurrent writes, missing idempotency, unique keys, transaction order, or remote state drift. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce INVALID_CROSS_REFERENCE_KEY affected user or permission response

A Salesforce affected user or permission note for INVALID_CROSS_REFERENCE_KEY: authorization failure caused by missing role, stale owner, key mismatch, inherited deny, WAF policy, or object-level permission. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY affected user or permission response

A Salesforce affected user or permission note for CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY: DNS resolution failure caused by missing records, wrong authority, stale TTL, policy records, or service target mismatch. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce MIXED_DML_OPERATION affected user or permission response

A Salesforce affected user or permission note for MIXED_DML_OPERATION: duplicate or lock conflict caused by concurrent writes, missing idempotency, unique keys, transaction order, or remote state drift. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce UNABLE_TO_LOCK_ROW affected user or permission response

A Salesforce affected user or permission note for UNABLE_TO_LOCK_ROW: duplicate or lock conflict caused by concurrent writes, missing idempotency, unique keys, transaction order, or remote state drift. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce LIMIT_EXCEEDED affected user or permission response

A Salesforce affected user or permission note for LIMIT_EXCEEDED: Salesforce failure caused by validation rule, governor limit, field-level security, API name drift, or automation order. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce INVALID_FIELD affected user or permission response

A Salesforce affected user or permission note for INVALID_FIELD: Salesforce failure caused by validation rule, governor limit, field-level security, API name drift, or automation order. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce Apex heap affected user or permission response

A Salesforce affected user or permission note for Apex heap: application runtime failure caused by exception, parser error, framework wiring, database adapter, automation trigger, or recursive call. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce INACTIVE_OWNER_OR_USER specific path failure response

A Salesforce specific path failure note for INACTIVE_OWNER_OR_USER: authorization failure caused by missing role, stale owner, key mismatch, inherited deny, WAF policy, or object-level permission. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce FIELD_CUSTOM_VALIDATION_EXCEPTION specific path failure response

A Salesforce specific path failure note for FIELD_CUSTOM_VALIDATION_EXCEPTION: Salesforce failure caused by validation rule, governor limit, field-level security, API name drift, or automation order. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce DUPLICATE_VALUE specific path failure response

A Salesforce specific path failure note for DUPLICATE_VALUE: duplicate or lock conflict caused by concurrent writes, missing idempotency, unique keys, transaction order, or remote state drift. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce INVALID_CROSS_REFERENCE_KEY specific path failure response

A Salesforce specific path failure note for INVALID_CROSS_REFERENCE_KEY: authorization failure caused by missing role, stale owner, key mismatch, inherited deny, WAF policy, or object-level permission. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY specific path failure response

A Salesforce specific path failure note for CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY: DNS resolution failure caused by missing records, wrong authority, stale TTL, policy records, or service target mismatch. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce MIXED_DML_OPERATION specific path failure response

A Salesforce specific path failure note for MIXED_DML_OPERATION: duplicate or lock conflict caused by concurrent writes, missing idempotency, unique keys, transaction order, or remote state drift. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce UNABLE_TO_LOCK_ROW specific path failure response

A Salesforce specific path failure note for UNABLE_TO_LOCK_ROW: duplicate or lock conflict caused by concurrent writes, missing idempotency, unique keys, transaction order, or remote state drift. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce LIMIT_EXCEEDED specific path failure response

A Salesforce specific path failure note for LIMIT_EXCEEDED: Salesforce failure caused by validation rule, governor limit, field-level security, API name drift, or automation order. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce INVALID_FIELD specific path failure response

A Salesforce specific path failure note for INVALID_FIELD: Salesforce failure caused by validation rule, governor limit, field-level security, API name drift, or automation order. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce Apex heap specific path failure response

A Salesforce specific path failure note for Apex heap: application runtime failure caused by exception, parser error, framework wiring, database adapter, automation trigger, or recursive call. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce INACTIVE_OWNER_OR_USER proxy versus origin split response

A Salesforce proxy versus origin split note for INACTIVE_OWNER_OR_USER: authorization failure caused by missing role, stale owner, key mismatch, inherited deny, WAF policy, or object-level permission. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce FIELD_CUSTOM_VALIDATION_EXCEPTION proxy versus origin split response

A Salesforce proxy versus origin split note for FIELD_CUSTOM_VALIDATION_EXCEPTION: Salesforce failure caused by validation rule, governor limit, field-level security, API name drift, or automation order. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce DUPLICATE_VALUE proxy versus origin split response

A Salesforce proxy versus origin split note for DUPLICATE_VALUE: duplicate or lock conflict caused by concurrent writes, missing idempotency, unique keys, transaction order, or remote state drift. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce INVALID_CROSS_REFERENCE_KEY proxy versus origin split response

A Salesforce proxy versus origin split note for INVALID_CROSS_REFERENCE_KEY: authorization failure caused by missing role, stale owner, key mismatch, inherited deny, WAF policy, or object-level permission. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY proxy versus origin split response

A Salesforce proxy versus origin split note for CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY: DNS resolution failure caused by missing records, wrong authority, stale TTL, policy records, or service target mismatch. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce MIXED_DML_OPERATION proxy versus origin split response

A Salesforce proxy versus origin split note for MIXED_DML_OPERATION: duplicate or lock conflict caused by concurrent writes, missing idempotency, unique keys, transaction order, or remote state drift. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce UNABLE_TO_LOCK_ROW proxy versus origin split response

A Salesforce proxy versus origin split note for UNABLE_TO_LOCK_ROW: duplicate or lock conflict caused by concurrent writes, missing idempotency, unique keys, transaction order, or remote state drift. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce LIMIT_EXCEEDED proxy versus origin split response

A Salesforce proxy versus origin split note for LIMIT_EXCEEDED: Salesforce failure caused by validation rule, governor limit, field-level security, API name drift, or automation order. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce INVALID_FIELD proxy versus origin split response

A Salesforce proxy versus origin split note for INVALID_FIELD: Salesforce failure caused by validation rule, governor limit, field-level security, API name drift, or automation order. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce Apex heap proxy versus origin split response

A Salesforce proxy versus origin split note for Apex heap: application runtime failure caused by exception, parser error, framework wiring, database adapter, automation trigger, or recursive call. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce INACTIVE_OWNER_OR_USER timeout and load response

A Salesforce timeout and load note for INACTIVE_OWNER_OR_USER: authorization failure caused by missing role, stale owner, key mismatch, inherited deny, WAF policy, or object-level permission. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce FIELD_CUSTOM_VALIDATION_EXCEPTION timeout and load response

A Salesforce timeout and load note for FIELD_CUSTOM_VALIDATION_EXCEPTION: Salesforce failure caused by validation rule, governor limit, field-level security, API name drift, or automation order. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce DUPLICATE_VALUE timeout and load response

A Salesforce timeout and load note for DUPLICATE_VALUE: duplicate or lock conflict caused by concurrent writes, missing idempotency, unique keys, transaction order, or remote state drift. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce INVALID_CROSS_REFERENCE_KEY timeout and load response

A Salesforce timeout and load note for INVALID_CROSS_REFERENCE_KEY: authorization failure caused by missing role, stale owner, key mismatch, inherited deny, WAF policy, or object-level permission. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY timeout and load response

A Salesforce timeout and load note for CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY: DNS resolution failure caused by missing records, wrong authority, stale TTL, policy records, or service target mismatch. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce MIXED_DML_OPERATION timeout and load response

A Salesforce timeout and load note for MIXED_DML_OPERATION: duplicate or lock conflict caused by concurrent writes, missing idempotency, unique keys, transaction order, or remote state drift. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce UNABLE_TO_LOCK_ROW timeout and load response

A Salesforce timeout and load note for UNABLE_TO_LOCK_ROW: duplicate or lock conflict caused by concurrent writes, missing idempotency, unique keys, transaction order, or remote state drift. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce LIMIT_EXCEEDED timeout and load response

A Salesforce timeout and load note for LIMIT_EXCEEDED: Salesforce failure caused by validation rule, governor limit, field-level security, API name drift, or automation order. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce INVALID_FIELD timeout and load response

A Salesforce timeout and load note for INVALID_FIELD: Salesforce failure caused by validation rule, governor limit, field-level security, API name drift, or automation order. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce Apex heap timeout and load response

A Salesforce timeout and load note for Apex heap: application runtime failure caused by exception, parser error, framework wiring, database adapter, automation trigger, or recursive call. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce INACTIVE_OWNER_OR_USER cache or propagation drift response

A Salesforce cache or propagation drift note for INACTIVE_OWNER_OR_USER: authorization failure caused by missing role, stale owner, key mismatch, inherited deny, WAF policy, or object-level permission. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce FIELD_CUSTOM_VALIDATION_EXCEPTION cache or propagation drift response

A Salesforce cache or propagation drift note for FIELD_CUSTOM_VALIDATION_EXCEPTION: Salesforce failure caused by validation rule, governor limit, field-level security, API name drift, or automation order. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce DUPLICATE_VALUE cache or propagation drift response

A Salesforce cache or propagation drift note for DUPLICATE_VALUE: duplicate or lock conflict caused by concurrent writes, missing idempotency, unique keys, transaction order, or remote state drift. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce INVALID_CROSS_REFERENCE_KEY cache or propagation drift response

A Salesforce cache or propagation drift note for INVALID_CROSS_REFERENCE_KEY: authorization failure caused by missing role, stale owner, key mismatch, inherited deny, WAF policy, or object-level permission. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY cache or propagation drift response

A Salesforce cache or propagation drift note for CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY: DNS resolution failure caused by missing records, wrong authority, stale TTL, policy records, or service target mismatch. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce MIXED_DML_OPERATION cache or propagation drift response

A Salesforce cache or propagation drift note for MIXED_DML_OPERATION: duplicate or lock conflict caused by concurrent writes, missing idempotency, unique keys, transaction order, or remote state drift. It includes evidence, output examples, branches, and the smallest reliable fix.

Salesforce UNABLE_TO_LOCK_ROW cache or propagation drift response

A Salesforce cache or propagation drift note for UNABLE_TO_LOCK_ROW: duplicate or lock conflict caused by concurrent writes, missing idempotency, unique keys, transaction order, or remote state drift. It includes evidence, output examples, branches, and the smallest reliable fix.