splitch

DocsAPITARGETING_KEY_MISMATCH.md

TARGETING_KEY_MISMATCH

HTTP status
409
Recommended action
CREATE_NEW_RUN
Details payload
{ currentTargetingKey: string, attemptedTargetingKey: string, experimentId: string, recommendedAction: RecommendedAction }

Cause

The Targeting Key changed on a Run that is already assigning traffic. Every Entity would rebucket, and the Exposures already recorded would describe a different population than the ones that follow.

Fix

Start a new Run with the new Targeting Key. The old Run keeps its measured cohort intact; the new one buckets from scratch.

Related codes