Decide where the work belongs
Describe the consequence
For each gap, record the workflow that cannot be confirmed, endpoint reach, last known state, pending recovery, and whether a duplicate or loss is possible. Distinguish an operator unable to explain an event from a customer outcome already affected.
Compare safe evidence paths
Assess adding bounded identifiers, retaining stage timestamps, repairing a worker handoff, reviewing a delivery, or requesting sender evidence. Keep raw content and secrets out of routine traces. Record owner, reversible containment, and the evidence each option would add.
Set a queue position
Put state-changing gaps and shared correlation breaks first, then isolated display or report omissions. Attach a fixture, review date, and threshold that would move the item. Keep an endpoint with unknown retention behavior provisional rather than ranking it from volume alone.
What to carry forward
Return a ranked tracing queue with consequence, scope, safe containment, owner, and evidence threshold. Escalate gaps that hide durable state or recovery. Keep the rank provisional when endpoint history, sender delivery, or downstream completion remains unobserved.
Technical background: Zendesk developer documentation.
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