Build a useful investigation brief
Reconstruct the state machine
List every observed transition with timestamp, deployment identity, environment, and source. Compare the sequence with the expected release stages and identify the first missing or contradictory transition.
Check alternate evidence
Look for runtime version, traffic routing, health observations, approval records, or a replacement deployment that could explain apparent stagnation. Link exact records and keep delayed ingestion as a possible explanation.
Separate hold from failure
Test whether exposure is unchanged, partially advanced, or serving an unexpected version. A rollout can be waiting safely, waiting with customer impact, or failing while its status remains stale; describe which evidence supports each possibility.
What to carry forward
The investigation brief should show the expected and observed transition sequences, current exposure evidence, and the first unexplained gap. Conclude with a bounded classification such as reporting delay, held progression, or unresolved execution state, with confidence and next evidence. Compare the missing transition with adjacent rollouts and record whether the same state source lagged there; repeated gaps suggest an observability boundary, not necessarily rollout failure.
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