Establish what is happening
State the freshness contract
Write the expected update interval, the timestamp that defines freshness, and any accepted delay during maintenance or source quiet periods. Identify whether users need latest state, latest event, or a periodic snapshot. Avoid labeling a quiet source stale without checking its activity.
Pair source and destination
Select entities with recent source changes and compare source version or update time with destination value, ingestion time, transformation time, and last successful read. Record the first boundary where the newer state disappears, including any delivery or batch window evidence available.
Bound lag and impact
Measure lag by source, entity type, update age, and processing revision. Identify reports, joins, exports, or user decisions using stale values. Separate a broad delay from isolated entities and distinguish missing updates from updates that arrived but were not rendered or queried.
What to carry forward
Return a freshness brief with the contract, paired timestamps, first lag boundary, affected cohorts, and downstream impact. Triage is complete when stale observations are reproducible and a responsible stage is named. Keep the cause open when source activity or destination read evidence is incomplete.
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