Hi team! We at

groover

have experienced the same issue twice recently, for the projects

hype-rollout

and

curator-onboarding

, and are concerned about what’s happening. In both cases, we were in the process of setting up a test/rollout, where in our

dev

and

staging

test envs, users received the treatment experience. However, the prod env was not rolled out in Growthbook (0% treatment / 100% control). We received reports in both cases of users seeing the test/feature live in prod, when it was not yet fully developed, leading to customer frustration. In response, we then set our dev envs to 0%, and the issue disappeared. Could there be cross-environment pollution happening? We’re nervous that this could potentially affect our test results as well. Please advise, thank you! 🙏

Are your different environments using different SDKs?

Nope, they’re the exact same sdks (on vue 3)

what about sdk connections?

You should have a different SDK endpoint per environment

ah yes, there are different endpoints/env, our issue is that sometimes it “flashes” other test cells that are not the control one

ah, client side SDK?

Thank you! We’ll look into this