Build a useful investigation brief
Prepare a controlled priority pair
Create sanitized urgent and lower-priority jobs that become ready in a known order and can be recognized by one trace. Record the expected precedence and keep their execution cost comparable. Repeat once with the worker pool quiet and once with ordinary background load.
Trace queue-to-worker selection
Follow each job through enqueue, ready state, queue assignment, poll, claim, and start. Capture the selector inputs and worker eligibility at the point of choice. A lower-priority job starting first is meaningful only if both jobs were simultaneously eligible.
Test one policy boundary
Change one bounded dispatch setting or queue arrangement in the fixture and rerun the pair. Compare ready-to-claim order and downstream result. If the urgent job still waits because no worker is eligible, record capacity as a separate finding rather than calling it inversion.
What to carry forward
Deliver a matched dispatch trace, policy comparison, first ordering divergence, and one tested boundary. Name whether the smallest fix belongs to priority propagation, queue topology, selector logic, or capacity. Preserve a limitation when the fixture cannot make both jobs eligible together.
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