Archive / Topic
#replay
5 posts, newest first
Before you replay, ask what the customer can already prove
Recovery decisions get narrower when the case starts with the evidence already visible to the customer
Three facts a replay screen must show before resend
A replay control gets safer when the operator sees identity, surviving evidence, and duplicate risk before motion begins
Replay blocks should name the boundary
Recovery gets slower and riskier when the record says replay is unavailable but hides the exact condition that makes another send unsafe
Replay the oldest uncertain receipt first
When a backlog mixes accepted, unknown, and lookup-ready failures, queue order is a weak way to decide what deserves human attention first
A manual replay needs the reason that justified it
An operator-triggered replay is safer when the system preserves why the original uncertainty was judged replayable at all
Often tagged alongside replay