Statsig local overrides never touch the console and are not a full mock

TL;DR

Use overrides for local dev scenarios, not as a test double for the whole evaluation path. If QA needs a known value everywhere, set it in the console.

Steps

1. Use overrides for local dev scenarios, not as a test double for the whole evaluation path.
2. If QA needs a known value everywhere, set it in the console.

When to use

You are seeing this: The docs also warn the override API is not designed to be a full mock, it is just a convenient way to force a value while testing. Use this skill when you run into "Statsig local overrides never touch the console and are not a full mock".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Statsig local override APIs only change what the SDK returns on that machine. They do not update the gate or config definitions in the console or anywhere else. The docs also warn the override API is not designed to be a full mock, it is just a convenient way to force a value while testing.

Verified resolution: Use overrides for local dev scenarios, not as a test double for the whole evaluation path. If QA needs a known value everywhere, set it in the console.

Source URL: https://docs.statsig.com/server/ruby