Check whether the outcome improved
Replay the original failure pattern
Use the same route, method, input structure, account class, release assumptions, timing, and dependency conditions from the baseline. Repeat enough attempts to exercise both observed outcomes. Record status, error type, trace boundary, visible feedback, and state changes rather than counting only successful responses.
Check retries and state integrity
Exercise an explicit retry, a delayed response, and a failure after partial work where safe. Confirm the client knows whether retry is allowed, logical writes occur once, and records are neither missing nor duplicated. Compare before and after state with identifiers and timestamps.
Probe neighboring error paths
Test validation, authorization, empty, dependency, timeout, and recovery cases that share the route. Confirm each status and error object remains meaningful and no broad rescue converts distinct failures into success. Check the original workflow from first input through final usable state.
What to carry forward
Classify the result as resolved, regressed, unchanged, or inconclusive with matched outcomes, state, and error evidence attached. It passes only when the original action behaves consistently or reports a safe failure, retries have clear ownership, and no neighboring path loses correctness.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow