Check whether the outcome improved
Define record outcomes
Write expected fields, review state, replay eligibility, redaction, and owner for transient failure, exhausted event, missing ID, prior effect, and closure. State which cases must remain quarantined. Keep replay eligibility beside the failure.
Run review paths
Create failed records and inspect search, detail, owner, and replay controls. Confirm event and delivery IDs remain distinct, history is ordered, and safe metadata survives redaction. Do not use real secrets or payloads.
Check bounded replay
Replay only an eligible synthetic event, then repeat it and review an ineligible record. Verify deduplication, side-effect count, and closure state. Ensure a missing or expired record cannot be replayed through a generic action.
What to carry forward
Accept when failed records are findable, histories and redaction are clear, replay eligibility is explicit, and effects remain bounded. Keep coverage partial for sender-only history. Record fixtures, retention, review owner, and replay results. Confirm that marking a record reviewed cannot independently trigger another delivery or hide a failed replay attempt.
Technical background: Twilio 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