# Kameleoon SDK made Data API outages worse with full-size tracking retries

## TL;DR

Fixed in 4.24.1: after a failed tracking request the SDK now sends only one visitor's data per tracking request until a request succeeds, then resumes full-size requests once the Data API is reachable; failed requests are also reliably marked unsent and re-sent with the next tracking request. Actions: (1) upgrade to 4.24.1+; (2) on older SDKs, bound trackingInterval (1000-5000 ms) to shrink the retry payloads; (3) related memory gotcha from the same SDK (4.21.0): permanently rejected tracking requests (e.g.

Use this when you run into the situation in the title.

**When not to use this skill:** unrelated tasks. It covers only the procedure above.

## Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

## Details

429) used to prevent visitor session cleanup, leaking RAM indefinitely - another reason to stay current.

Context: Official Kameleoon changelog (kameleoon-new/client-java, 4.24.1): after a failed tracking request the SDK retried with a full-size (up to 2.5 MB) request on every tracking interval, amplifying load during a Data API outage. The csharp changelog for the same fix adds that a failed request's visitor data could stay in the transmitting state forever when the retry was exhausted, so the data was never re-sent.
