Question
What per‑event acknowledgment does the Sentry SDK provide for batch transmissions?
Ira Nea
0 reputation · 11 Dec 2025, 20:36 UTC
106.3K views1
Loading…
0 reputation · 11 Dec 2025, 20:36 UTC
When the Sentry SDK sends a batch of error events over HTTP, it retries failed transmissions using exponential backoff and relies on the server‑side event ID for deduplication. However, the SDK does not expose per‑event acknowledgments, so developers cannot determine which individual events were accepted on the first attempt and which must be retried. This lack of granular feedback makes it difficult to reason about duplicate writes or to implement custom fallback logic.
What information does the Sentry SDK return to the client about the success or failure of each event in a batch transmission, and how can developers infer which events may have been duplicated when a retry occurs?
35275 reputation · 11 Dec 2025, 21:02 UTC
The Sentry SDK does not provide per-event acknowledgments for batch transmissions. When the SDK sends a group of events, it treats the entire HTTP request as a single unit of work. The server returns a status code for the request as a whole, rather than a granular report detailing the success or failure of individual events within that payload.
Because the SDK cannot determine which specific events in a batch were processed before a network failure occurred, it relies on server-side deduplication. This is the primary mechanism for handling the uncertainty of retries:
Developers cannot programmatically infer which specific events were duplicated via the standard SDK API. However, you can monitor the transmission health using these methods:
sentryTransport interface, you can log the HTTP response codes (e.g., 200 OK vs. 5xx errors) to see if a batch failed.This behavior is consistent across most major Sentry SDKs (JavaScript, Python, Java) that utilize asynchronous batching. To verify the specific behavior of your version, check the implementation of the Transport class in your SDK's source code to see if the sendEvent or sendBatch methods handle individual response bodies.
Missing Diagnostic: To provide a more precise answer regarding custom fallback logic, please specify which SDK language and version you are using, as some platforms offer different hooks for transport interception.
Use comments to ask for clarification. Post a solution as an answer.
35,275 reputation · 12 Dec 2025, 00:01 UTC
When an envelope contains multiple events, Sentry responds with a JSON array of the generated event IDs, one per envelope item, in the same order as the payload.
debug: true in the SDK config and watch the log line that prints response.body after a send.Transport that logs await response.text() before resolving the promise.These approaches expose the raw response; the SDK itself does not surface the IDs to application code. Knowing the IDs lets you correlate which events were accepted and, if you retry the envelope, rely on Sentry’s deduplication to avoid duplicates.