Decide where the work belongs
Rank by freshness breach
For each cohort, compare observed age with the documented expectation and record the dependent decisions or displays. Give priority to stale values that can trigger a current action, while keeping broad but harmless delays visible. Include both oldest age and number of affected entities.
Assess growth and recovery
Compare lag over successive observations and identify whether new changes continue to accumulate. Classify recovery as deterministic replay, source clarification, blocked dependency, or uncertain. Queue forward recovery before historical refresh when the destination is still falling behind.
Choose a queue outcome
Select investigate now, coordinate a dependency, perform a bounded refresh, clarify the freshness contract, or monitor. Name owner, cohort, evidence source, and escalation trigger. Do not prioritize a resync solely because data is old if the source has not produced a newer authoritative state.
What to carry forward
Return a ranked stale-sync queue with freshness breach, consequence, lag trend, recovery confidence, owner, and next evidence. The top item should identify what decision is currently at risk. Keep rankings provisional where source activity, destination read timing, or the freshness expectation is not established.
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