Lost Update

A lost update happens when one operation replaces another operation’s change without accounting for it. If two workers read a counter of ten and both save eleven, one increment disappears.

Atomic database expressions, version checks, or locks can protect the update, depending on the workflow. Reading a value and later writing a replacement is unsafe when concurrent changes are possible unless the intervening state is checked or protected.