Before the repairNo request guard
Old result takes over
HistoryToday
Run the example to see the request order.
App repair / interactive example
Keep the screen
the user chose.
Two requests. The wrong one arrives last. See a small change keep an old result from replacing your latest choice.
Synthetic demonstration. Responses and delays are simulated. No customer app, data or external service is involved.
After the repairLatest request only
Latest choice stays
HistoryToday
Run the example to see the request order.
History starts first; Today finishes first. The repaired version should stay on Today.
A small repair.
A clear boundary.
Each new request gets a number. Only the latest request may update the screen, including its error state. A failed current request stops loading and can be retried.
This demonstrates one repair, not the cause of a problem in your app. It does not cancel network requests or establish broader production reliability.
How we scope a real repair