# Inaccurate Freshness

**URL:** <https://community.pinecone.io/t/inaccurate-freshness/8459>\
**Category:** Support\
**Tags:** serverless, freshness\
**Created:** [November 8, 2025, 4:14am UTC](https://community.pinecone.io/t/inaccurate-freshness/8459 "2025-11-08T04:14:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ajohnston](https://sea2.discourse-cdn.com/flex020/user_avatar/community.pinecone.io/ajohnston/32/3876_2.png) [@ajohnston](https://community.pinecone.io/u/ajohnston)\
**Post date:** [November 8, 2025, 4:14am UTC](https://community.pinecone.io/t/inaccurate-freshness/8459/1 "2025-11-08T04:14:43Z")

</div>

We have been using freshness via the API, rather than the Python SDK, for several months now. By that I mean we upsert large batches of vectors, get the `x-pinecone-request-lsn` value from the response, then use `/query` to find out what the `x-pinecone-max-indexed-lsn` is, polling until that is at or larger than the largest LSN we got from each of the upserts.

At some point that seems to have broken, and our integration code hasn’t really changed at all for this since we added it, at least not for this part. Consider the following psuedo-code:

```auto
target_lsn = upsert_all(…)
wait_for(target_lsn)

while True:
  results = query({ a filter matching the unique metadata of the vectors that were just upserted })
  print(results)

```

Particularly when a lot of vectors were uploaded, the first few queries return no results. We don’t use a top\_k, so even nothing was even close to being a good match, it should have returned something. But the first few queries get nothing. Then suddenly, with no further calls to Pinecone on our end, and with the same LSN still present, we get results after a little bit, presumably after it’s actually caught up on freshness.

So, it _seems_ like there’s an issue with freshness. No matter what, it should have gotten _something_ from Pinecone, but it gets nothing. And then suddenly gets results, making me think the freshness LSN is inaccurate in some way. Any help would be appreciated, this is a considerable problem on our end, though we can mitigate it to an extent for now. 🙂

Other notes:

- We use a serverless index.
- We embed with OpenAI
- Paid account, no issues otherwise, no errors

---

<div class="post-metadata">

**Author:** ![perry](https://sea2.discourse-cdn.com/flex020/user_avatar/community.pinecone.io/perry/32/1729_2.png) [@perry](https://community.pinecone.io/u/perry)\
**Post date:** [November 10, 2025, 8:43pm UTC](https://community.pinecone.io/t/inaccurate-freshness/8459/2 "2025-11-10T20:43:48Z")

</div>

> [@ajohnston](#):
>
> Then suddenly, with no further calls to Pinecone on our end, and with the same LSN still present

This _sounds_ like maybe something to do with asynchronous requests getting processed later in your application?

Could you open a support ticket so we can look into this for you?