Serious Vector Store bug!

Heads up! If you’re building an integration, there’s a nasty bug in Vector Store management you need to be aware of.

Last week, we created around 5 vectors stores using the UI and then around 15 vector stores through the API. We decided to delete the 15 API created stores using the UI, one by one. At around deletion number 9 or so, we encountered an error on the UI and suddenly, we weren’t able to list our stores.

We immediately went to the API to query the list all stores endpoint at https://api.openai.com/v1/vector_stores which we know works because is a fundamental component in our integration project. Unfortunately, this had also stopped working as well.

Whereas before, it would list our vector stores, now it just returns:
{
“error”: {
“message”: “Vector store not found”,
“type”: “invalid_request_error”,
“param”: null,
“code”: null
}
}

When we try and list our vector stores on the website, we just get a red error message on the screen which says:

”An unexpected error occurred. Vector store not found” in red text.


This is a big deal for us as we’re writing an integration into openAI which relies on the ability to list the stores and that’s now somehow broken and despite asking for help, a week later, we’re still down!

I’ve spoken to the help GPT bot thing again and again requesting someone to look at this but it’s an absolute waste of time! How can an integrator like ourselves build services around these API’s when the platform operator provides absolutely zero service level!

So in desperation, I’m turning to the community… Does anyone have any ideas on how to fix this? Has anyone else had this? Being able to list our vector stores is critical to not only our project, but also our billing. We’re completely stuck!

2 Likes

The only solution that is apparent, since there is no acknowledgement of this continued issue is:

  • maintain your own listing of vector store IDs.
  • create a new project if you must try to start again, which will mean all-new scoped data such as conversations
  • do not rely on the list method by API either
1 Like

@darren5

A few bugfixes have been rolled out since this topic has been created.
Do you still have this issue?

I’ve just checked, no we still have exactly the same issue.

This is the result of the API call:

And this is in the UI:

2 Likes

This should be fixed now! We saw the issue on the vector store dashboard too, deployed a fix, and is no longer seeing the error. Can you go and try the vector store dashboard again to see if works?

2 Likes

Did you observe it on one particular project and on that projects API calls also, where it is impossible to get an organization’s listings of vector stores because of damaged listings inside. Then switch to another project, see success in listing or an empty list with no errors, then go back to the original project and again get a broken vector store listing?

It is not a platform site issue, it is not platform site code or making bad requests or the URL showing wrong info: it is a data corruption issue. Multiple forum reports, no remedy.

Those experiencing the issue by platform site API call, that is exactly mirrored on the API endpoint when called by project API keys, can sometimes work around what appears to be a damaged vector store ID index by making API calls and listing with a very low limit or limit=1, or by changing descending order to ascending to avoid where the listing issue occurs. That demonstrates it is the DATA.

If you did not identify this issue instead of a happenstance “we saw something too”, track organizations and replicate the fault on their projects, and deliver a solution to the database itself, it cannot be considered repaired. You are just waiting for even more developers to enter the realm of failure, when their own store listing gets messed up. Developers that have continued to have issues must be pinged. Like:

@_j I couldn’t reproduce the issue even after creating and deleting a thousand vector stores, but with the details from affected users the team was able to pinpoint the cause and deploy a fix.

We’re all hoping this is finally resolved for good.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.