I was able to access my vector stores earlier today, but a few hours ago, I suddenly got this error message: “An unexpected error occurred: Vector store not found”. I checked my project’s storage on OpenAI Platform page, but that too displays the same error. Anyone else having issues accessing their vector stores?
Yes, I’m seeing the same thing. This occurs both using the API vectorStoreClient.GetVectorStores and also on the dashboard page.
Any help appreciated!
Something to note that can be “user error” - files storage, vector stores, and responses server-side objects are now finally and completely scoped to a project, with no cross-project access possible. Even fine tuning is broken by being pinned to a project and inaccessible.
Maybe the reason for repeated days-long downtimes and continued issues that persist with corrupted listings or inability to list vector stores, failures to delete (and continued billing of file attachments you deleted and vector stores you cannot delete) and failures to attach and poll.
This means that it is too easy to simply use a different API key and get an unexpected error, the error being that your project is locked out due to scoped resources.
The same thing just happened to me.
I’ve been deleting some test vector stores I had created, and when I reloaded the page, it showed me this message.
I don’t know if the problem is just mine or general.
Regards
It’s just you - but not only you.
You likely have a damaged listing of vector stores, like others have experienced. Even using the API to list vector stores, you could experience errors, and by listing with "limit":1, in asc or desc order, you might discover one call can be successful, and then the expanding the listing with a larger limit will break the listing, or even have different counts below the limit per-call.
This type of vector store problem has been pervasive and unresolved by OpenAI, and can be newly created also, not just past corruptions by something now fixed.
The issue and a partial workaround is that you might be able to get partial listings via API calls, delete a few, but there are still unlistable IDs that you continue to get billed for daily.
You can likely create or use a new project, create a vector store there (as they are now scoped), and list successfully. Or without creating, receive a report about the list being empty and not an error.
Ultimately, OpenAI will have to fix what they broke with vector stores and fix organization projects, and fix their own organization so this type of issue does not continue.
Thanks for your answer.
I’m getting the same error via the SDK. I’ll try retrieving the items one by one to see if I can avoid the error.
Regards
I can confirm that using limit < x works. However, when I reach a specific record, it throws an error. It seems there’s a corrupted record preventing further listing.
Regards.
1 Like
The problem is pervasive enough that I posted a script to look for this and find the limit count where an API call would avoid the error (like you would have written) - 18 days ago.
The case there was so problematic for that developer that different “limit” inputs each gave wildly different results counts before ultimately discovering where a query completely broke the endpoint.
The beauty of “we use AI to push PRs when they seem to work” - nobody has ownership or knowledge of the code base, because nobody actually wrote it, the application slowly breaking down into unmaintainable slop the more AI you use.