Check whether the outcome improved
Verify the quiet control
Run the low-priority job with no competing favored arrivals. Confirm it claims and completes through the documented path. This establishes that eligibility, worker routing, and terminal handling work before fairness pressure is introduced.
Verify mixed arrivals
Interleave favored and low-priority jobs with known ready times. Check that the favored stream retains its declared precedence while the low-priority job receives a bounded service opportunity. Record claim age and any changed completion order.
Verify sustained pressure
Keep favored arrivals available across several worker slots and observe the low-priority witness. Confirm it eventually claims or reaches an explicit aging or review state. Reconcile the favored jobs’ outcomes so fairness did not hide failed or abandoned urgent work.
What to carry forward
Accept when the low-priority job receives the promised eventual service or explicit review state under the sustained fixture, while favored work retains its contract. Record the measured comparison without inventing a universal threshold. Reopen verification if eligibility disappears or service is obtained only by losing urgent work.
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