Check whether the outcome improved
Replay allowed and rejected requests
Use the original route, actor scope, resource, request mix, concurrency, and window conditions. Record each decision, response status, metadata, retry signal, and client-visible message. Repeat with a separate actor or resource so a scoped limit is not accidentally shared across unrelated work.
Check reset and retry safety
Observe behavior before, during, and after the stated reset boundary. Follow the intended retry rule and confirm repeated attempts do not create duplicate writes or amplify demand. Check timeout, server error, validation, and rate-limit responses remain distinct for client handling.
Exercise fairness and critical recovery
Run a noisy actor beside a normal actor and exercise the critical action previously blocked. Confirm unrelated work proceeds according to the policy, the critical workflow receives understandable recovery, and a successful retry produces one correct final state. Record any starvation or scope leakage.
What to carry forward
Classify rate-limit behavior as correct, regressed, unchanged, or inconclusive with scope, reset, retry, fairness, and workflow evidence attached. It passes only when intended requests are protected, rejected callers can recover safely, unrelated actors remain appropriately isolated, and state stays correct.
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