Decide where the work belongs
Separate exposure from visibility
Ask whether traffic reached the wrong environment or whether only the record points there. Evidence such as routing, version markers, and service logs can distinguish user risk from an investigation blind spot.
Assess decisions at risk
List release, rollback, verification, and incident decisions that depend on the mismatched record. Give higher priority to ambiguity that could permit further exposure or conceal a failing path.
Pick an evidence deadline
Set a review time tied to the next deployment stage, verification window, or affected customer path. Assign the smallest context repair or comparison that can reduce uncertainty without changing authority or release behavior.
What to carry forward
The queue result should say whether the mismatch blocks a release decision, threatens users, or mainly delays reporting, with an owner and evidence deadline. If exposure cannot be ruled out, preserve higher priority until environment identity is verified.
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