Audit webhook retries and duplicate acknowledgments
Group a webhook delivery log by endpoint and event ID to distinguish retries, repeated acknowledgments and missing success responses.
How this check works
Inputs and matching rules
Use the following exports: Delivery attempts.
- Group exact endpoint and event ID pairs.
- Count only HTTP 200–299 as acknowledgments.
- Keep unknown outcomes distinct from confirmed non-2xx responses.
Read the evidence
In the sample, orders/evt-02 returns 503 and then 200, while orders/evt-03 has a single 500. They need different follow-up. An event ID used on two different endpoints is not automatically a duplicate.
What the result can establish
Use one row per delivery attempt and stable endpoint aliases. A 2xx confirms a response, not downstream completion. This check does not contact endpoints.