Check whether the outcome improved
Define rollover outcomes
Write expected verification, receipt, retry, and review state for old, new, overlap, expired-old, wrong endpoint, missing configuration, and receiver restart. State which cases remain quarantined. Keep each endpoint version explicit.
Run secure transition cases
Execute fixtures with receiver before and after deployment, then compare endpoint and version labels, signature result, and event identity. Confirm a temporary overlap does not silently permit an unrelated secret or endpoint. Log the safe version label.
Check failed delivery recovery
Process a failed synthetic event after configuration correction through the approved path. Verify deduplication, side-effect count, and logs remain safe. Keep the event rejected while secret version is ambiguous. Retain the endpoint and revision beside the result.
What to carry forward
Accept when intended versions verify through a documented transition, wrong or missing secrets fail, and pending recovery preserves identity without duplicate effects. Keep sender overlap partial when uncontrolled. Record labels, deployment revision, fixtures, and results.
Technical background: Stripe 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