Webhook intake idempotency and fan-out scoping fixes
NousResearch/hermes-agent · cluster 7448 · gateway
Data as of
Nothing open on GitHub. Fix merged in #130692. Check it covers your case.
The short answer
- Known?
- Yes. 7 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #130692. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #130692. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and pull requests address problems with webhook idempotency keying and deduplication logic that caused multi-route fan-out scenarios to incorrectly skip valid deliveries. The work focuses on scoping idempotency and dedup per route rather than globally by delivery ID alone.
Open issues0
Open PRs0
Fixes on record
-
#130692 fix(gateway): webhook deliveries on different routes or profiles no longer drop each other as duplicates (#7448, salvage #129626)
files:
gateway/platforms/webhook.py,tests/gateway/test_webhook_adapter.py,tests/gateway/test_webhook_integration.py,website/docs/guides/webhook-github-pr-review.md,website/docs/user-guide/messaging/webhooks.md
5 PRs closed without merging
From the close comments: superseded by another PR 2 · PR volume cleanup 1 · duplicate 1 · merged via another change 1
- #7471 fix(webhook): scope idempotency per route · PR volume cleanup
-
#33321 fix(webhook): scope GitHub delivery dedup by route · duplicate →
#24633,#7448 -
#85618 fix(webhook): make intake fan-out-safe and structurally valid (Webhook Revolution) · superseded by another PR →
#85523 -
#90236 fix(webhook): close Task 10 intake identity and raw-bound contracts · superseded by another PR →
bd3fd0e,c30ac90,#97083 -
#106922 fix(webhook): scope delivery idempotency keys by route · merged via another change →
5a8dea8,#7448,#130692
Closed issues · 1
- Closed#7448Webhook idempotency is keyed only by delivery ID, so the second route is skipped in valid multi-route fan-out
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.29: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- gateway
- Merged PRs
- #130692
- Closed issues
- 1
- Attempts
- 5 PRs closed without merging
- Fix link checked
- 1 Oct 2026