ReviewOS

stacks/ts-analytics

No idempotency: at-least-once delivery double-counts events

#169
Closed glennmichael123 opened this 9 days ago ·
9 days ago

Every write mints a fresh server-side id; replaying an identical beacon produced two rows (live-verified). SQS consumer is explicitly at-least-once with no dedup. Fix: tracker-minted per-event UUID, derive sk from it, attribute_not_exists conditional put; same in the SQS consumer.

From the production-readiness audit (docs/research/production-readiness.md, eacf996). Verified with live probes where stated.

9 days ago

Fixed — tracker-minted per-event eid + EIDLOCK conditional put (24h TTL), fail-open on non-conditional errors. Live-verified: same eid twice → stored once.

Sign in to comment on this issue.