Feature request · API & developer experience · Blocks work
Idempotency key to avoid duplicate events from server retries
1 source thread · first seen 2023-08
Summary
A developer sending subscription events from a server can double-send after a crash and retry, corrupting sales and MRR data, and wants an idempotency key or sender-generated event id. Persisting IDs first risks never sending the event.
- Affects
- developer sending server-side revenue events
- Workaround
- Persist unique IDs in a database before sending, with the risk of lost events
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“Some way to ensure idempotency when sending events to posthog so on the posthog side there's no duplicates”