Establish what is happening
Anchor expected progress
Record the deployment reference, target environment, expected transitions, and the time each should have occurred. Use the release plan or owner statement as the expectation, and mark expectations that were never written down.
Read the last transition
Capture the latest status, timestamp, commit or artifact, exposure marker, and related event. Check whether new evidence is arriving under another identifier or environment before concluding that the rollout stopped.
Bound user exposure
Determine what version currently serves traffic and whether exposure is expanding, held, or unknown. Separate a progress-reporting gap from a rollout execution problem, because their immediate risks differ.
What to carry forward
Triage is complete when expected milestone, last known transition, current exposure, and evidence gap are explicit. Escalate a potentially stalled rollout when exposure or recovery options are uncertain; otherwise classify it as delayed reporting with a review time. Capture the last trusted observation before the gap and the first record after it, if any; this prevents a quiet reporting interval from being mistaken for a halted transition.
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