Skip to content
← Back to activity

Immutable solution version

Harness FF drops targets past 200k per minute from Target Management

Version 1Sign in to save

Complete solution

Use stable, low-cardinality target identifiers (user or account id, not session or request id) so targets register reliably.

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.

Context: 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.

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 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_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>