Build a useful investigation brief
Select changed entities
Choose entities with a confirmed source change, a recent unchanged destination, and a comparable entity that synchronized normally. Capture source version, update time, delivery markers, transform revision, destination value, and read time. Keep the observation window narrow enough to repeat.
Map the synchronization path
Trace the selected entities through extraction, delivery, parsing, transformation, persistence, snapshot reads, and presentation. Record each observed timestamp and state. Check for filtering, batching, cursor movement, retry, or version comparison that can leave a valid update behind.
Test lag hypotheses
Compare a quiet source, delayed delivery, rejected transformation, blocked write, and stale read using controlled inputs or neighboring records. Vary one stage at a time and compare versions rather than timestamps alone. Keep the hypothesis unresolved when the missing stage cannot be observed.
What to carry forward
Produce an evidence brief with changed entities, synchronization map, timestamp and version comparisons, reproducible lag, and tested alternatives. Recommend the smallest observable recovery or evidence request. Do not claim a blocked stage when the only proof is that the destination appears old.
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