OhMyBug

logic/correctness

Mid-lifecycle status change not handled

#55rare5 sightingsfirst seen September 2026

What goes wrong

A consumer sets an object's state from its creation or final event and never handles the transition events in between. When the state flips mid-way (pending to failed, inquiry to chargeback), the mirror is never updated.

Example

A payment webhook handler processes 'created' and 'succeeded' but not 'disputed', so chargebacks never appear in the order status.

Not to be confused with

The first event is handled; this is not a missed cache refresh within one process (Missed Snapshot Refresh) and not an entry point that skips a policy check.

Discovered by

Field notes · 1