Skip to content
Kumiko

stale_state

What happened

Someone else modified this item in the meantime. Please reload the page and try saving again.

Technical background

ConflictError fires when an atomic UPDATE lost the optimistic- locking race — another writer moved the row between our snapshot and our WHERE clause.

Default client SDK behavior: toast a “please reload” message and re-fetch the entity.

To customize conflict handling per entity, see optimistic locking configuration.