WebhookAdapter: idempotency cache #818
Notifications
Due Date
No due date set.
Blocks
Depends on
Reference: sam/archie#818
Reference in new issue
Block a user
Implement TTL-based idempotency cache to deduplicate retried webhook deliveries. Cache based on webhook event ID and route.
Notes
Not started. No cache of any kind in internal/channels/webhook/webhook.go. Needs a webhook event ID (route-scoped) -> TTL cache; most platforms send a stable delivery/event ID header (e.g. GitHub's X-GitHub-Delivery) usable as the key. Related to the gateway-level archie-core-1786637492498-104-1bde76ae (MessageDeduplicator) which solves the same class of problem one layer up -- check whether one mechanism can serve both before building a second cache.
Close reason
Superseded: the WebhookAdapter design is replaced by event capture (t2db): captures, event types, mappings by example, bindings and CEL playbooks. Retry dedup filed as its own t2db bead.
Imported from beads
archie-core-1786637497328-286-9c985f28· GitHub #307 · type task · priority P2 · created 2026-08-08 · closed 2026-10-05