Check whether the outcome improved
Verify below and at the ceiling
Run the fixed job mix at the lower control and selected setting. Confirm completed item count, claim age, retries, errors, and shared-resource readings meet the stated expectation. Read durable outcomes after workers settle so partial work is not hidden by an early throughput sample.
Verify above the ceiling
Exercise the higher setting that previously showed pressure. Confirm the expected guard or isolation applies and record the resource and queue behavior. The test should demonstrate why the ceiling exists, not merely show that a lower number is different.
Verify neighboring job classes
Run an unaffected class beside the constrained class and compare its service and resource use. Check that the ceiling does not starve another queue or exhaust a shared connection pool. Reconcile retries and terminal states for both classes.
What to carry forward
Accept when the selected ceiling preserves correctness and useful service, keeps the identified resource within its stated guard, and does not displace neighboring work unexpectedly. Record the tested workload limits. Reopen verification when a new job shape, dependency, or resource path bypasses the evidence.
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