Skip to content

[AI-FSSDK] [FSSDK-12958] Continue rule evaluation after local holdout hit - #525

Open
alexjoeyyong wants to merge 1 commit into
masterfrom
ai/alexjoeyyong/FSSDK-12958-local-holdout-flow-fix
Open

alexjoeyyong wants to merge 1 commit into
masterfrom
ai/alexjoeyyong/FSSDK-12958-local-holdout-flow-fix

Conversation

@alexjoeyyong

@alexjoeyyong alexjoeyyong commented Oct 13, 2026 •

Copy link
Copy Markdown

Summary

A local holdout hit used to return the holdout variation and stop evaluating the flag. Now it excludes the user from that rule only: the hit is recorded, the rule is skipped, and evaluation continues with the next rule, so the user can still be served by a later rule.

Changes

  • Local holdout hits on experiment and delivery rules skip that rule and continue to the next rule instead of returning
  • Each local holdout hit sends one holdout impression in the existing format, regardless of sendFlagDecisions
  • Local hits reuse the existing mechanism for global holdouts bypassed by excludeTargetedDeliveries
  • The final decision and its events are unchanged; global holdouts are unchanged

Jira Ticket

FSSDK-12958

Notes

  • Legacy APIs (is_feature_enabled, get_feature_variable_*) now skip a locally held-out rule without sending a holdout impression, matching how they already treat excludeTargetedDeliveries holdouts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant