Vector Store API calls returning 504s, 503s, and generally being slow

Hey @Con, that can definitely be frustrating.

Since you've already tried a few approaches, one workaround that has helped others is treating the update as a migration rather than modifying the existing vector store:

• Create a new vector store for the updated resource set
• Add files in batches to reduce write pressure during ingestion
• Wait until ingestion is fully complete
• Run a small smoke test against the new store
• Update the assistant to use the new vector store ID
• Keep the previous vector store temporarily as a rollback option
• Delete the old vector store only after the new one is confirmed stable

This isn't ideal, but it can help avoid issues during large updates or re-indexing operations.

Props to @S_z too

Avinash