Build a useful investigation brief
Build a freshness timeline
Order write or transition, response, partial replacement, cache read, navigation, and visible render timestamps. Record request URLs, filters, record identifiers, and any delayed processing that changes the sequence.
Compare read paths
Inspect full page, Turbo visit or frame, browser reload, back-forward cache, and new-session behavior. Identify the first path that serves old content and whether it shares a cache key or fragment.
Test competing causes
Check missed persistence, delayed event processing, incorrect record scope, stale client state, and cache invalidation as possibilities. Use authoritative data to rule out a display-only conclusion.
What to carry forward
The brief should identify the first stale read or render boundary, authoritative state, affected paths, and competing explanations. Conclude cache invalidation, update delivery, persistence, scope, or unresolved with evidence and confidence. Compare response headers or freshness markers where available with server-rendered content, Turbo visits, back navigation, and a new session to locate the first stale boundary. Record whether the stale value survives a direct request, which helps separate server freshness from client history 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