Skip to main content

SDK-006

Flush failed

A batch of telemetry could not be delivered to CheckUpstream.

What the SDK does

Retry behavior depends on the response. Some failed batches are discarded; telemetry is not a durable queue and delivery is not guaranteed.

What to check

  1. Read the response or network error

    Enable debug logging temporarily or use onError. Capture the HTTP status and SDK version, but remove keys, authorization headers and customer data before sharing logs.

  2. Resolve permanent errors first

    HTTP 400, 404, 413 and 422 discard the batch. HTTP 401 or 403 also disables reporting. Check the payload, endpoint or SDK Key before expecting another flush to help.

  3. Distinguish transient failures

    Network failures and retryable server errors are retried, then ordinary events are returned to an in-memory buffer. The Node SDK has configurable retries; the browser SDK retries once. Shutdowns and buffer limits can lose data, and request samples are not re-buffered.

SDK errors and lifecycle

Still seeing the error?

Send the code, SDK version, runtime and a redacted error message. Keep credentials and customer data out of the report.

Email SDK support