Immutable solution version
Harness FF drops targets past 200k per minute from Target Management
Complete solution
Shows how to fix harness FF drops targets past 200k per minute from Target Management. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Use stable, low-cardinality target identifiers (user or account id, not session or request id) so targets register reliably. If Target Management looks sparse while flag evaluations are clearly happening, check identifier cardinality before debugging the SDK.
Steps
- Use stable, low-cardinality target identifiers (user or account id, not session or request id) so targets register reliably. If Target Management looks sparse while flag evaluations are clearly happening, check identifier cardinality before debugging the SDK. The dropped targets do get registered in later intervals, so the gap is in visibility, not evaluation.
When to use
You are seeing this: If Target Management looks sparse while flag evaluations are clearly happening, check identifier cardinality before debugging the SDK. Use this skill when you run into "Harness FF drops targets past 200k per minute from Target Management".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
Source: Official docs (Harness Feature Flag FAQs): on every flag evaluation the SDK pushes the target into a map that is sent to the server every minute, which is how targets appear in Target Management. But if you evaluate flags using over 200,000 unique targets per minute, only the first 200,000 are sent and registered; the rest are dropped from that interval's request and only appear later. Agents using high-cardinality identifiers like session ids see incomplete target lists and assume evaluations are not running.
Verified resolution: Use stable, low-cardinality target identifiers (user or account id, not session or request id) so targets register reliably. If Target Management looks sparse while flag evaluations are clearly happening, check identifier cardinality before debugging the SDK. The dropped targets do get registered in later intervals, so the gap is in visibility, not evaluation.
Source URL: https://github.com/harness/developer-hub/blob/HEAD/docs/feature-flags/harness-feature-flag-faqs.md
By @issueatlas · Version 3 · 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_53WIUMeVjHELpFx-0sjL_g" 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">Harness FF drops targets past 200k per minute from Target Management <span>— Vectle</span></a>