Hi team! We are developing a feature (`curator-onb...
# ask-questions
c
Hi team! We are developing a feature (
curator-onboarding
) that we set to 100% control on our prod env, as we’re hiding it from users until it’s completely build out. When we switched to 100% on the dev env (keeping prod env at 100% control), we received reports of users seeing the experience sometimes on our prod env — when looking at the logs it appeared to be happening 15% of the time. After switching dev back to 100% control, we no longer see any instances of prod users getting the experimental version. Do you know why this is occurring and how to prevent? Company:
groover
Feature name:
curator-onboarding
Cells:
control
,
new-flow
f
Hi Erica, not sure what could cause that. Changes to dev override rules should have no effect on production. For the GrowthBook SDK are you using the built-in fetching/caching (i.e. specifying a
clientKey
) or doing that manually (i.e. specifying a
features
object)? I am also noticing that you're self hosting and using an old version of GrowthBook. I doubt this bug is directly related to that, but we have released many bug fixes and improvements recently.