When a feature gate is set to Launched
or Disabled
, it will always return the default value (TRUE for Launched, FALSE for Disabled) and stop generating billable exposure events. However, disabling a feature gate will not stop checks against it - it'll just always return false. Removing it from your codebase will stop checks - assuming you don't have any old versions of your code still running anywhere.
If you're still seeing checks after that, it's possible that there might be some instances where the gate is still being referenced. Double-check your codebase to ensure that all references to this gate have been removed. If the issue persists, it is recommended to flag this issue to the Statsig team for further assistance.
In some cases, you might still see exposure events in Stitch for gates you've launched/disabled (and all are presumably False
). This could be due to a bug in the system. The Statsig team is always ready to identify and fix such issues.
Please note that fixes for such bugs are usually rolled out promptly and should resolve over a short period of time. However, if you're still not seeing the issue as resolved on your end, it is advisable to reach out to the Statsig team for further investigation and assistance.