Keep the lesson for the next incident
Compare repeated pairs
Group episodes by component pair, contract, environment, queue, and release sequence. Distinguish expected overlap from pairs that repeatedly produce uncertain or harmful outcomes.
Document the transition
Record the intended compatibility window, participant identities, and evidence that demonstrates safe coexistence. Keep the statement conditional if compatibility was inferred rather than observed.
Create a recognition rule
Define a future review when an incompatible version pair reaches the same boundary or persists beyond its expected window. Name the reviewer and the records needed to decide quickly.
What to carry forward
The lesson should preserve one explicit compatibility boundary and a recurrence rule for version pairs outside it. Treat the rule as provisional until subsequent releases show that old workers, queues, and regions are included in review. Retain a compatibility matrix with served and intended versions, contract checks, and an explicit transition window so later releases can distinguish expected overlap from unreviewed skew.
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