Salesforce Error Troubleshooting Guide

This error occurs when a custom validation rule prevents a record from being saved. The validation rule evaluates to true, blocking the operation.

This error occurs when a user tries to create or update a record that references another record they don't have access to, typically due to sharing rules or field-level security.

This error occurs when trying to insert or update a record with a value that violates a unique constraint, such as a duplicate email, external ID, or unique field.

This error occurs when attempting to save a record without populating a required field. The field may be required at the object level or by a validation rule.

This error typically occurs when trying to activate or modify a metadata component (like a workflow, flow, or validation rule) that has errors or dependencies.

This error occurs when trying to set a field that cannot be modified, such as a formula field, auto-number field, or system field that's read-only.

This generic error occurs when attempting an operation that's not allowed, such as deleting a record with dependencies or modifying a locked record.

This error occurs when an invalid Salesforce record ID is provided. IDs must be 15 or 18 characters and match the expected format for the object type.

This error occurs when trying to save a text value that exceeds the maximum length allowed for the field.

This error occurs when the wrong data type is provided for a field, such as trying to set a number field with text or a date field with an invalid format.

This error occurs when trying to access or reference a record that has been deleted, typically in a lookup or master-detail relationship.

This error occurs when a trigger tries to update the same record that triggered it, creating a recursive loop that Salesforce prevents.

This error occurs when a SOQL query is malformed, references non-existent fields, or violates query rules.

This error occurs when a process exceeds Salesforce's governor limits, such as too many SOQL queries, DML operations, or CPU time.

This error occurs when authentication fails, typically due to incorrect credentials, expired sessions, or security token issues.

This error occurs when using queryMore() with an invalid or expired query locator, typically in pagination scenarios.