Error123

Governor limits cap what one transaction can consume, and exceeding one throws a System.LimitException that cannot be caught with try/catch. The whole transaction rolls back. The fix is always to use less of the...

The record is locked, normally because it is pending in an approval process. Common causes How to fix

The org has run out of data or file storage, so new records cannot be created. Common causes How to fix

A trigger tried to update or delete a record that is already being processed by a trigger in the same transaction. Common causes How to fix

A value supplied as an ID is not a valid Salesforce ID for that field. Common causes How to fix

The operation targets a record that has been deleted. Common causes How to fix

Setup objects and regular objects were modified in the same transaction. Setup objects include User, UserRole, Group, GroupMember, PermissionSet, PermissionSetAssignment and QueueSObject. Common causes How to fix

A trigger or flow threw an unhandled exception during the save. This code is a wrapper. The real cause follows in the message. Common causes How to fix

Salesforce could not get an exclusive lock on a record within about 10 seconds. The message reads unable to obtain exclusive access to this record. Common causes How to fix

The request tries to write to a field that cannot be written. The message reads Unable to create/update fields: <field>. Common causes How to fix