Loading

Collision Detection error 'Changes cannot be saved' when a record is edited

Publiceringsdatum: May 24, 2026
Beskrivning

When editing a record — via either a full edit or an inline edit for standard objects that use Aura record home — a Collision Detection error may appear if another user, the same user in a different browser window (Lightning Experience only), or a background process has changed the same record during your edit session.

Salesforce Classic Error Message

"Changes Cannot Be Saved. The record you were editing was modified by User during your edit session."

Lightning Experience Error Message

"This record was modified by (User) during your edit session. Make a note of the data you entered, then reload the record and enter your updates again."

Note: When making an inline edit for all custom objects and standard objects that use LWC record home, the record page automatically refreshes unless another user, the same user in another window, or a background process edits the same field to a different value. In that case, instead of the message above, users see a message showing the conflicting field values and can choose which values to keep.

Lösning

Why Does This Happen?

This error is caused by a built-in security feature called Collision Detection. Collision Detection prevents a user from saving record changes if the record was modified by another user, process, or browser session since the edit began. This feature cannot be disabled and is in place to prevent possible data loss.

How to Resolve the Error

To resolve the error, reload the record and re-enter your changes before saving again.
Example: If Sales Rep A opens an Opportunity to update the Close Date, and Sales Rep B saves a change to the same Opportunity first, Sales Rep A will see the Collision Detection error. To resolve this, Sales Rep A should note their intended changes, click Reload on the record page, and re-enter the updates before saving.

Knowledge-artikelnummer

000385614

 
Laddar
Salesforce Help | Article