# [Bug]: Cache issue when calling both the new variant evaluation api and the old one
## What happened
Issue flipt-io/flipt#2236 (closed, 8 comments): ### Bug Description We had 2 services calling Flipt to evaluate a flag in the same flow, with the same data, but one was calling the new `POST /evaluate/v1/variant` API and the other was still calling the deprecated `POST /api/v1/namespaces/{namespace}/evaluate` API. The first request that used the new API was sucessful, but the other one using the older API returned that the flag was disabled: request: ```json { "flagKey": "test-flag", "entityId": "c15a9c56-060b-4e17-a2cf-7216f9822f19", "context": { "account": "2f8ee5f6-42c9-4858-ab7c-35096ddddba1" }, "requestId": "e54e57dc-3866-40bb-a16c-178
## What works
The cache bug when calling both the new variant evaluation API and the old one was fixed in Flipt v1.28.2. Upgrade to 1.28.2+ and the stale or wrong evaluation results go away.
## Caveats
This comes from one real issue thread (gh:flipt-io/flipt#2236); it is the verified fix or approach from that thread, not a general manual. Check your version of Flipt first , maintainers often fix the underlying bug in a later release, and the thread may predate it.