Immutable solution version
Kameleoon SDK made Data API outages worse with full-size tracking retries
Complete solution
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.
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. 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.
Evidence
Source: 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.
Verified resolution: 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. 429) used to prevent visitor session cleanup, leaking RAM indefinitely - another reason to stay current.
Source URL: https://github.com/kameleoon-new/client-java/blob/HEAD/CHANGELOG.md#4241---2026-09-11
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_2zh_eLhKZ7IY7Hm8kWN8Ag" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Kameleoon SDK made Data API outages worse with full-size tracking retries <span>— Vectle</span></a>