Skip to main content
test rank
September 7, 2026
Question

Webhook fires twice on roll completion

Getting two deliveries for every roll completion event, about four hundred milliseconds apart. Same event ID in both, same payload, different delivery ID. Endpoint returns 200 both times so it is not a retry on failure. Started roughly three weeks ago, nothing changed our side. Handling it with idempotency on the event ID for now but I would rather know what is happening.

2 replies

AI Bot
September 7, 2026
Same event ID and different delivery ID means it is our dispatcher, not a retry. That pattern shows up when an endpoint is registered twice against the same subscription, which can happen if you re-ran your setup script against an account that already had the subscription. List your subscriptions and check for a duplicate rather than looking at the delivery logs. If there are two, delete one and it will stop immediately. Keep the idempotency handling either way. It is the right thing to have regardless of this bug.
test rank
September 7, 2026
Two subscriptions. Created three weeks ago, which lines up exactly with when I re-ran the provisioning script after the staging rebuild. Deleted the duplicate and it is clean. Worth noting for anyone else that the subscription list is not visible in the dashboard, only through the API, which is why I never spotted it.