How to Debug Webhook Replay and Duplicate Delivery
Debug webhook replay, duplicate delivery and out-of-order events by checking event ids, signatures, timestamps, retries and receiver idempotency.
Quick Answer
Webhook senders often retry delivery, and some dashboards allow manual replay. Receivers must treat delivery as at-least-once, verify signatures, store event ids, ignore duplicates safely and handle events that arrive late or out of order.
Example Scenario
A webhook receiver processes the same invoice event twice. The provider dashboard shows a retry after a timeout, and a support engineer also clicked replay. The payload is valid, but the receiver created duplicate internal work because it deduped by timestamp instead of event id.
Step-by-Step Explanation
- Verify the signature before processing.
- Store provider event ids or delivery ids.
- Check retry and manual replay history.
- Handle out-of-order events with resource version checks.
- Make processing idempotent.
- Log duplicate decisions without logging secrets.
Start by Naming the Contract That Broke
Webhook duplicate delivery is expected behavior when providers use at-least-once delivery and replay tools. Debugging is slower when every symptom is treated as a generic API failure. Name the contract first: request shape, response shape, retry behavior, file type, time zone, numeric precision, logging policy or delivery semantics. Once the contract is named, each observation has a place to belong.
The most useful first signal is usually the same event id arriving more than once. It tells you which boundary produced the failure and prevents the team from rewriting unrelated client code. Keep the original request, response or log line available while you investigate.
A good working note should say what was expected, what actually happened and which layer observed it. That note is more valuable than a screenshot of a stack trace because it can be compared with documentation, tests and production logs.
If the issue is intermittent, keep one failing sample and one passing sample from the same release window. The passing sample prevents overfitting the fix to one user, while the failing sample keeps the investigation grounded in evidence instead of guesses about the system.
Separate Symptoms from Evidence
The visible symptom may be a timeout or manual replay in provider delivery logs, but the evidence should be more precise. Capture signature timestamp and event id from the raw delivery, then compare it with a successful case from the same environment. Environment, user role and feature flag differences can otherwise look like code regressions.
Avoid starting with broad fixes. First check provider retry history and receiver response status. If that detail differs from the healthy request, you have a concrete lead. If it matches, move to the next layer instead of guessing.
When multiple teams are involved, preserve the raw evidence in a safe form. Redact secrets, but keep field names, status codes, headers, timestamps and request ids. Sanitized evidence still lets another team reproduce the reasoning.
Look for Boundary Translation Errors
Many production bugs happen when data crosses a boundary and changes meaning. A browser form, generated client, proxy, queue worker, database mapper or logging pipeline can transform the value before the final system sees it.
For this issue, inspect the internal side effect created by each delivery. That is where small differences usually become visible. A value may still look reasonable to a human while failing the receiver's stricter expectation.
Use comparison tools when the payload is large. Diff the failing sample against a known-good sample, then reduce it to the smallest input that still fails. A minimal failing sample turns a vague incident into a contract discussion.
Boundary errors also need ownership clarity. Decide which component is allowed to transform the value and which component must reject it. Without that decision, every layer may add a small compatibility patch, and the system becomes harder to reason about after the incident.
Choose a Fix That Matches the Failure Mode
The first safe fix is often storing processed event ids before non-idempotent side effects. It addresses the observed boundary instead of hiding the symptom. If the problem is a contract mismatch, the fix should update the producer, consumer or documented contract deliberately.
The second fix to consider is checking resource version before applying older events. This is useful when old clients, partner integrations or delayed deployments mean two shapes must be accepted for a short time. Compatibility should be explicit and temporary where possible.
A third option is adding explicit duplicate and replay log decisions. Use this when the system needs better operational visibility before making a behavioral change. Good diagnostics can prevent a small correction from becoming a larger regression.
Keep Production Diagnostics Safe
Diagnostics should explain the failure without exposing sensitive data. For this topic, useful logs include request id, status code, safe field paths, environment and a short reason code. They should not include tokens, full personal records or secret payloads.
If the failure reaches support, include event id, delivery id and processing decision in receiver logs. That gives the next debugger a trail without requiring access to private customer data. It also helps separate one-off bad input from a systemic contract drift.
When adding logs, add deletion and retention awareness. Debug logs that are safe today can become risky if they accumulate raw payloads for months. Prefer structured fields over copied bodies.
A safe diagnostic should also be cheap to leave in place. If it requires developers to enable raw payload logging during every incident, the next emergency will recreate the same privacy and security risk. Prefer stable reason codes, counters and compact metadata that can remain active in production.
Prevention Checklist
Add a regression test for provider retry, manual replay and out-of-order event cases. The test should fail when the boundary behavior changes unexpectedly. A small test around the contract is often more valuable than a broad snapshot that nobody reviews.
Review webhook receiver idempotency during integration release during release. Many bugs in this category appear during rolling deploys, integration updates or data migrations, not during a clean local run.
Document which event identifier is stable enough for dedupe. The goal is not a long policy page; it is a short, accurate rule that future developers can apply while changing the same path.
After the fix, replay the original failing case and one known-good case. If both behave correctly, record the evidence in the incident or changelog. This closes the loop and keeps the next investigation from starting over.
Code Examples
if (await seen(event.id)) {
return new Response('duplicate', { status: 200 });
}
await markSeen(event.id);if (event.created < resource.lastProcessedEventTime) {
console.log('Ignoring older event', event.id);
}console.log({ eventId: event.id, deliveryId, type: event.type, duplicate });Common Mistakes
- Assuming webhooks are delivered exactly once.
- Deduping by timestamp instead of event id.
- Processing before signature verification.
- Treating manual replay as a different business event.
- Failing on duplicates instead of acknowledging them safely.
FAQ
Are duplicate webhooks normal?
Yes. Many providers use at-least-once delivery and retries.
Should duplicates return an error?
Usually no. Acknowledge safe duplicates so the provider stops retrying.
Can webhook events arrive out of order?
Yes. Use resource version or event time checks where order matters.
What should be logged?
Event id, type, delivery id, response status and duplicate decision, not secrets.