Affected: All SDKs
Overview
This topic explains why you may still see unexpected flag variation events in your flag evaluations graph, even after expecting them to stop. All analytics data originates from the SDKs you are using. In some cases, a variation that should no longer be served may continue to show up in analytics with a small percentage of events each day.
This can happen for several reasons, including:
- Cached variations being served while a context is offline or the app is backgrounded, until the SDK reconnects to LaunchDarkly and receives updated flag values
- A team member triggering the flag during local testing
- An older version of the application still running and sending events for that flag variation
Solution
To investigate and resolve this issue:
-
Check with your team members to confirm no one is still using that flag variation locally.
-
Use our Data Export integration to inspect which contexts are receiving the variation in question.
-
Review your usage dashboard to identify connections from unexpected versions. If any are found, you may need to investigate whether older application code is still in use and evaluating the flag.
To proactively monitor this behavior in the future, use our SDK’s evaluation reasons feature to determine which variation is being served and why.