OhMyBug

concurrency/state

Superseded attempt still accepted as current

rare41 sightingsfirst seen September 2026

What goes wrong

Work is replaced by a newer attempt, but nothing durable marks which attempt is the current one. When the older request, response, or holder finally lands, it is treated as valid and takes effect. The reader relies on the newer attempt having displaced the older one, when that displacement was never recorded anywhere the late arrival can check.

Example

A retried job finishes, then the attempt it replaced returns and its result is stored, because neither carried any marker saying which attempt was current.

Not to be confused with

Not Timeout Leaves Work Running: the superseded attempt completes and its effect is accepted as current, because no marker tells the attempts apart, not merely because old work was never stopped.

Discovered by

Field notes · 9

Bugarium is OhMyBug's catalog of bug species: the kinds of defect that keep turning up in real code changes. Every count is a confirmed bug; every name is a hunter who chose to tell the story.