Aglet

Verify priority ordering across queues and worker classes

Verification should test the priority contract where it is meant to apply and expose cases where capacity or queue separation changes the result. Exercise matched jobs, tied ready times, and an urgent late arrival. Compare claim order, not just completion, and retain the queue and worker context for every result.

Check whether the outcome improved

  1. Verify a same-queue pair

    Release urgent and lower-priority jobs together to an eligible worker pool. Confirm the documented claim order and record both ready and start timestamps. If work finishes in a different order because durations differ, keep the claim evidence as the priority result.

  2. Verify queue and class boundaries

    Repeat the pair across each supported queue or worker class where priority is advertised. Confirm whether the contract is global or local and that the observed behavior matches its wording. Record a deliberate isolation rule as expected behavior, not an inversion.

  3. Verify ties and late arrivals

    Release equal-priority ties and an urgent job after lower-priority work has already been claimed. Check stable tie handling and confirm a late job cannot preempt an in-flight step unless that behavior is explicitly supported. Read final statuses for collateral failures.

What to carry forward

Accept when claim order matches the stated scope of the priority contract across eligible queues and classes, with ties and late arrivals documented. Keep capacity limits visible. Reopen verification if a job loses its priority label or a consumer assumes global precedence that dispatch does not promise.

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