Hi there wave We re working with the growthbook python sdk a

Question

Hi there wave We re working with the growthbook python sdk and we found an unexpected behaviour Let me address it and share the details in the thread below point down

kind-airplane-15946 · Answer

feature list js

kind-airplane-15946 · Answer

Given the feature list JSON above

kind-airplane-15946 · Answer

And the following python code that implements a callback function that just print the info implements a for loop that iterates over a range of integer values for the `shopper id` and fixed the `company id` to a specific value

kind-airplane-15946 · Answer

python code py

kind-airplane-15946 · Answer

It doesn t return any output when the expected output would be forcing the `bar` variation

kind-airplane-15946 · Answer

However when changing the fixed `company id` to 2 then it returns the following output

kind-airplane-15946 · Answer

We ve tried also with different configurations but always it seems that the condition rule to force specific variants is not working as expected Mentioning also some team members < elegant flag 19390> < green jordan 83609>

future-teacher-7046 · Answer

The trackingCallback only runs for experiments so if the value was forced from a non experiment rule it will not be called

future-teacher-7046 · Answer

The idea is that you would use force rules to exclude some people from the experiment and assign them specific values And then for the people who are part of the experiment they would be randomly assigned and you would track the exposure

kind-airplane-15946 · Answer

I believe we have configured it properly check out this screenshot

future-teacher-7046 · Answer

Only the first matching rule is used So that first force rule is stopping people from continuing on and being part of the experiment

kind-airplane-15946 · Answer

ok < future teacher 7046> the point you mentioned makes lot of sense So then how the python code knows when forcing values which flow variant should be used Maybe from the feature list JSON

kind-airplane-15946 · Answer

for instance in this case the forced value is `bar` when the condition applies

future-teacher-7046 · Answer

You would fork your code based on the value of the feature and not the variant number ```feature = gb evalFeature feature force value if feature value == bar ```

future-teacher-7046 · Answer

That way your code doesn t care if the value comes from an experiment or is forced If you stop the experiment you don t need a new code commit

future-teacher-7046 · Answer

Since you re using a string as the feature value instead of boolean the `isOn` and `isOff` methods aren t that useful since every string value besides an empty string will be considered on

kind-airplane-15946 · Answer

Totally understood now everything is clear from our side We could use this `getFeatureValue` and also this `evalFeature` Thanks so much for the clarifications and the quick response heart eyes