Check whether the outcome improved
Replay the original change
Use the same record, role, project, action, filters, and timing boundary from triage. Capture authoritative response and rendered state immediately and after the expected update delay.
Exercise every affected path
Review full navigation, Turbo or frame update, browser reload, back-forward navigation, and new-session behavior. Compare status, timestamps, ownership, and related records with the authoritative state.
Check delayed and empty states
Confirm pending processing remains labeled pending and missing records remain safely absent. Apply the freshness checkpoint and leave a follow-up if one cache or client path remains untested.
What to carry forward
Verification should state current across reviewed paths, partially current, still stale, or inconclusive. Close only when the original stale route reflects authoritative data and legitimate delays remain honestly labeled. Repeat the change through the normal workflow, then reload, revisit, and open a fresh session; confirm the visible state matches the authoritative record at each entry path. If one entry path remains stale, leave the result open and identify that path rather than averaging the outcomes.
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