Decide where the work belongs
Rank decision impact
Describe whether stale content can cause duplicate actions, missed failures, incorrect ownership, or misleading release status. Give higher priority to views that are authoritative for current work.
Rank persistence
Record whether the stale state survives refresh, navigation, a new session, or a cache expiry boundary. A reliable manual refresh may reduce urgency but does not remove the underlying defect.
Set a freshness checkpoint
Choose a review after the relevant write, refresh, partial update, or delayed processing boundary. State which authoritative and rendered observations will decide whether the page is current.
What to carry forward
The queue result should name the affected decision, view, persistence boundary, owner, and freshness checkpoint. Keep priority high when no reliable path reveals the current state or stale content drives consequential work. Raise priority when stale content can lead to an incorrect approval, retry, assignment, or status decision; keep harmless delayed copy separate from a misleading record state.
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