Latest Failed Record Hides Valid One

What goes wrong

A lookup takes the most recent record for a key by timestamp without filtering on validity, so a later failed, cancelled or otherwise ineligible record permanently hides the earlier valid one.

Example

Taking the newest payment attempt returns the failed retry, and the order shows 'unpaid' though the earlier attempt succeeded.

Not to be confused with

Picking by recency over rows of mixed validity; not a completion stamped too early (Premature Completion Certificate) and not a stale cache (Missed Snapshot Refresh).

Discovered by

@sks24git GitHub

Field notes · 5

@sks24git2026-11-02beat 2 review rounds

A skip rule reads "the latest past verdict" sorted by close time, but the verdict can be written after a newer record already closed. The newer skip then hides the fresh verdict, and retries stop.

Order by when the verdict was written, not by when the record closed. Late writes lose to early closes.

@sks24git2026-10-31beat 1 review round

A freshness alarm picked the latest result by last-update time and trusted any failure. A rerun of an old job, or the platform failing a job after a day in queue, looks fresh, so the alarm closes mid-outage.

Order runs by start time, not last update. Reruns touch old records.
Tell a job that never ran from a failed one. Timeouts dressed as results hide outages.

@sks24git2026-10-28beat 2 review rounds

A workflow gained a manual trigger whose UI defaults point at the main branch and fail a gate by design. The health monitor reads the newest run on main regardless of trigger, so one click opens a false red alarm.

A new trigger changes what "latest run" means. Re-check every reader that picks the newest run.
Filter monitors by event, not just by branch. Manual runs are not the branch's verdict.

@sks24git2026-10-28

A fix for a cancelled run's stale results said "only the newest run counts", but a newer lighter run never produces the checks the gate needs. The gate forgets a green full run and orders it again.

Filter by why a result is stale, not by age alone. Superseded is not the same as wrong.
Test the gate with runs of unequal shape. One shape hides the loss of names only the old run had.

@sks24git2026-10-23beat 2 review rounds

A new flag marked a link as switched off, but two older lookups still took the newest link without checking it. Switch off the newest of two links and the one still active gets refused as if nobody was there.

Grep every reader when you add a soft-delete flag. One missed query keeps picking the dead row.
Test with two rows, not one. A single row hides which one a query picks.