A feature flag obtained via refresh may override a feature flag with higher precedence.

[jimmyca15]

See this discussion for details of the original detection of this issue.

When using a setup like below to retrieve feature flags

.UseFeatureFlags(ffOptions =>
    { 
        ffOptions.Select(KeyFilter.Any, LabelFilter.Null);
        ffOptions.Select(KeyFilter.Any, "prod");
    });

It is expected that feature flags from the prod label override the flags with the null label. This works as expected as long as feature flags are not refreshed.

An issue can occur when feature flags are refreshed. When a change is detected for a feature flag with the null label, the new value will be used in the application. This happens even if there was a flag with the same name from the prod label that was in use.

Expected

No matter how many times I refresh feature flags, and regardless of what has changed, a feature flag with a higher precedence label will override a similarly named flag with the a lower precedence label.

Actual

If a feature flag with a low precedence label is changed and a refresh is triggered, that feature flag will override any feature flags with the same name even if they have a higher precedence.

[xelossan]

Are there any updates on this? We're having the same issue - sometimes flags with label are overwritten by values with null label, which is really bad.

[amerjusupovic]

Hi @xelossan, we're working on getting a fix out with the linked pull request for the next major version stable release. I can't give you an exact timeline on this at the moment but I can add an update here if anything changes.

[danyltsiv]

I can't reproduce the issue mentioned in this ticket, however, we have the same weird thing going on with feature flags. At some random moment, the value(false) from non-labeled overrides labeled ones(true). The weirdest part is that it randomly appears and randomly disappears, hard to find something that correlates with the issue to figure out the root cause. In our case, feature flags are manually updated, no automatism there, and there is no correlation between update times and issue times.

[muzopraha]

We have same issue on version 7.0.0