Hi, @calm-dog-24239 We’re experiencing an issue with GrowthBook feature flags. We update the feature flags, but the changes are never reflected on the client. The response always contains data with the last update timestamp:

"dateUpdated": "2026-06-30T16:06:59.273Z"

We’re using the GrowthBook Proxy, but we also tried connecting directly to GrowthBook and got the same result. This seems very critical for us.

Hi thanks for flagging this! Quick thing to check first: on the admin panel, are those feature changes actually published and not still in a draft? That's the usual reason

dateUpdated

stays frozen - the SDK only ever sees the last published state. Worth double-checking you're editing the same environment/project your SDK key points to too. Easiest way to confirm - hit the endpoint directly (no SDK), publish a change, hit it again, and see if

dateUpdated

moves:

curl -s "https://<your-host>/api/features/<your-sdk-key>"

If it doesn't budge even right after publishing, the stale data is coming from the server side, not the app. If publishing isn't it, drop us: • your`GBSDKBuilderApp(...)`init code • the`growthbook_sdk_flutter`version • and whether you're using *remote eval*(heads up: a remote-eval connection returns 400 on the normal`GET /api/features/<key>`)

Yes, the changes are published. We also verified that we’re using the correct environment and project. We tested by calling the endpoint directly (without the SDK), and the result is the same - no changes are reflected after publishing. So yes, it doesn’t seem to be a mobile app issue. We don’t use the

growthbook_sdk_flutter

we have our own implementation using remote evaluation. However, we reproduced the issue with a simple HTTP request as well, so the SDK isn’t involved.

Hi @busy-window-96391. Please let us check that.

@calm-dog-24239 Could you also let us know if there’s a maximum size limit for the response object? Are there any size restrictions we should be aware of?

Hi @busy-window-96391. Since you reproduced the issue with a raw HTTP request, this appears to be a server-side issue (Proxy/API cache), not a client SDK issue. A frozen

dateUpdated

indicates a stale cached payload. Two things to check: 1. Proxy cache – It should be invalidated via a webhook on publish. Could you check the Proxy webhook delivery/logs and clear its cache? (

CACHE_STALE_TTL

/

CACHE_EXPIRES_TTL

) 2. Endpoint/key – You mentioned using remote evaluation, but you're calling

GET /api/features/sdk-…

and receiving a

200

response. A remote evaluation connection uses

POST /api/eval/<key>

, and that

GET

request should return

400

. This suggests that the

sdk-…

key might point to a different SDK Connection than the one you're publishing to. Could you send the exact request URL along with a screenshot of the SDK Connection settings (remote evaluation enabled, environment, and project)? There is no silent payload size limit, and ~260 KB is well within the supported range, so that's not the cause.

We identified the root cause: it was caused by a fairly large audience configured for one of our experiments. Once we removed that audience, everything worked as expected. Thank you for your support!