# Pinecone takes about 2-3 minutes for upsert vector to be available for query **URL:** \ **Category:** Support\ **Tags:** vector-database, embeddings\ **Created:** [May 26, 2024, 2:41am UTC](https://community.pinecone.io/t/pinecone-takes-about-2-3-minutes-for-upsert-vector-to-be-available-for-query/5701 "2024-05-26T02:41:48Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![personaifydev](https://avatars.discourse-cdn.com/v4/letter/p/2bfe46/32.png) [@personaifydev](https://community.pinecone.io/u/personaifydev)\ **Post date:** [May 26, 2024, 2:51am UTC](https://community.pinecone.io/t/pinecone-takes-about-2-3-minutes-for-upsert-vector-to-be-available-for-query/5701/2 "2024-05-26T02:51:00Z")
How many vectors do you have in your index to reach up to 2-3 minute delay? Even with a brand new index, after upserting I have to wait 3-5 seconds before the query shows the data. This is already very bad from an automation perspective where my tests are then verifying or using the data. I either have to retry or sleep – neither of which is desirable. How are people handling this? This needs to be addressed. After upsert and return from the API, the data needs to be available. Also see ["There can be a slight delay before new or changed records are visible to queries"](https://community.pinecone.io/t/there-can-be-a-slight-delay-before-new-or-changed-records-are-visible-to-queries/4912) --- _[View the full topic](https://community.pinecone.io/t/pinecone-takes-about-2-3-minutes-for-upsert-vector-to-be-available-for-query/5701)._