Check whether the outcome improved
Define status outcomes
Write expected response, receipt, retry, review state, and effect for malformed, duplicate, transient, authorization, exception, and success cases. State finite handling for each disposition. Keep final state with every disposition.
Run the handler matrix
Execute fixtures and compare branch, status, body detail, durable receipt, event identity, and side-effect count. Confirm invalid input cannot retry forever and a duplicate after effect remains safe before response.
Check recovery and restart
Repeat a transient failure after recovery and an exception after receipt, including process restart. Verify pending work remains identifiable and a status change does not create a second mutation on restart.
What to carry forward
Accept when each handler outcome has the documented status, retry, receipt, and effect, with duplicates safe and recoverable events visible. Keep sender behavior partial when uncontrolled. Record matrix, handler revision, and final states. Repeat the temporary-failure case after recovery and confirm its final receipt differs from a permanent rejection, including after the receiver restarts.
Technical background: Zendesk developer documentation.
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