Decide where the work belongs
Name the urgent action
For each occurrence, write what the urgent job was supposed to unblock and whether a lower-priority job continued instead. Record the delay from ready to claim and any downstream deadline. Keep customer or operational consequence separate from a priority label alone.
Group by queue and worker class
Compare inversions within one queue, across queue partitions, and under a saturated worker pool. Note which combinations are confirmed and which are only suspected. A rule that fails only when queues are split needs a different owner from a selector that ignores priority everywhere.
Set a smallest next action
Choose immediate investigation, a queue-policy correction, or a matched dispatch experiment. State the missing timestamp or placement evidence that would change priority. Avoid moving all urgent work to a new queue before proving the current selection boundary.
What to carry forward
Queue the issue with the blocked urgent action, matched-order evidence, affected queue or worker class, and capacity context. Escalate when a documented priority is bypassed and downstream work is blocked. Otherwise schedule a dispatch investigation with a quiet and busy comparison.
Technical background: Rails guides.
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