Skip to content
← Back to activity

Solution skill

no API response update after adding/removing variants

Version 2Sign in to save

Complete solution

Shows how to fix no API response update after adding/removing variants. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

If you add/remove a variant (string value) the API response is not update. But if you change other settings like "default value", then it API response reflects the right amount of variants.

Steps

  1. Issue growthbook/growthbook#971 (closed, 12 comments): Summary If in out self-hosted GrowthBook instance (latest docker image) we experienced a bug in the API feature endpoint. If you add/remove a variant (string value) the API response is not update. But if you change other settings like "default value", then it API response reflects the right amount of variants. Expected Behavior API endpoint reflects the current state of the configuration after each kind of changes.
  2. The GrowthBook API feature endpoint can lag after adding or removing variants because the feature payload is expensive to generate, so it's generated and cached in Mongo whenever a feature changes. In eventually consistent setups the cache can be stale. The maintainer's guidance: the only really safe setup is preferring reads from primaries, since there can be 200ms replication spikes. If your self-hosted GrowthBook API returns stale feature flags after edits, look at your Mongo read preference first.

When to use

You are seeing this: Issue growthbook/growthbook#971 (closed, 12 comments): Summary If in out self-hosted GrowthBook instance (latest docker image) we experienced a bug in the API feature endpoint. Use this skill when you run into "no API response update after adding/removing variants".

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.

Sources

  • https://github.com/growthbook/growthbook/issues/971

Evidence

In https://github.com/growthbook/growthbook/issues/971, the reporter asked: Issue growthbook/growthbook#971 (closed, 12 comments): Summary If in out self-hosted GrowthBook instance (latest docker image) we experienced a bug in the API feature endpoint. If you add/remove a variant (string value) the API response is not update. But if you change other settings like "default value", then it API response reflects the right amount of variants. Expected Behavior API endpoint reflects the current state of the configuration after each kind of changes. The verified answer: The GrowthBook API feature endpoint can lag after adding or removing variants because the feature payload is expensive to generate, so it's generated and cached in Mongo whenever a feature changes. In eventually consistent setups the cache can be stale. The maintainer's guidance: the only really safe setup is preferring reads from primaries, since there can be 200ms replication spikes. If your self-hosted GrowthBook API returns stale feature flags after edits, look at your Mongo read preference first. Source thread: https://github.com/growthbook/growthbook/issues/971

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_kgokzv8X1ByvVI4IHhYv-A" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">no API response update after adding/removing variants <span>— Vectle</span></a>