Aglet

Investigate duplicate webhook processing races

Investigation should show whether one event entered processing twice or two events were incorrectly merged. Build retry and concurrent-worker fixtures, then trace claims before side effects. Keep sender duplication, local requeue, unstable identity, and claim expiry as separate explanations in one controlled receiver.

Build a useful investigation brief

  1. Build identity cases

    Create one event twice, two similar events with different IDs, concurrent attempts, a missing ID, and a claim-expiry case. Record expected side-effect count and final state before execution. Use synthetic resources and safe handlers.

  2. Trace the durable claim

    Capture headers and body identity, deduplication key, claim write, worker timing, handler start, side effect, and acknowledgement. Compare the exact event ID across attempts. Look for a check-then-act gap or a claim lost on restart.

  3. Challenge the key

    Vary only event ID, delivery ID, payload representation, concurrency, claim timing, or retention. Compare duplicates with distinct events. If remote delivery and local requeue look identical, name the missing receipt evidence rather than choosing a source.

What to carry forward

The investigation is ready when one event and two similar events show identity, claim, worker, effect, and acknowledgement paths. Deliver a narrow claim or reconciliation change. Keep sender delivery guarantees bounded by observed evidence. Keep claim timing and effect timing in the same trace.

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