For the last several days the vector store objects I’ve created disappear, files uploaded disappear, but they seem to remain attached to their respective assistants until that disappears too.
Is anyone else having the same problem or know what is going on?
I’m sorry to hear that, can you give me a bit more detail to help debug the issue. What is your organization id and which endpoints are things disappearing from?
Our organization ID is: org-fpnAeX6JRglMqW5PY9gETKhK
Thank you so much for jumping in to help. This is a very strange issue that has never happened before.
Currently I am creating vector stores and supplying them with files using the API Platform. I also use the API Platform to create the assistants. Everything else I manage remotely.
Here is a screenshot of the vector store list:
Several vector stores are missing. Here are some of their IDs:
vs_67cd245ddc308191887b994708648b9b
vs_67cd2b67228881918866b9488aafa760
vs_67ccd271cd9081918f49c8ddb3c6e153
There are a few more if you need them. Thank you.
I posted here a message because I’m experiencing something similar .
In my case what I think is playing an important role in making vector stores disappear, is the use of project keys.
It seems like creating/updating a store via CURL with project key changes some sort of internal status and from there on those stores are filtered out.
If I use a User key everything seems to work
Hope this helps
Yes there is currently a huge bug going on, and it should be classified as a CRITICAL OUTAGE!
Is there any update here?
The team has identified the issue, has a plan to fix it, and will be fixing it as soon as possible. Your vector stores are still in the system and usable, it is just the list vector stores endpoint that is impacted. We are planning to ensure all of your vectors stores show up in the list endpoint once we resolve the issue.
Perhaps you can detail if there will be any aspect of user data scoping to within projects now or in the future. This was hinted a bit early on, and there’s also a file upload purpose “user-data” that works similarly to “assistants”, but server-side client data such as threads, files, vector stores still seems basically organization-wide, bugs not withstanding.
The bug symptom hints at relation to scoping.
Do you have a timetable that you can share with the community?
Apologies for the delay, this one was very tricky to resolve. We believe the issue is resolved for all new vector stores and are working on backfilling all data that was not appearing. I don’t have an ETA on the backfill (we aren’t far enough along in the process to have a good guess at this point), but based on the timeline of this type of task previously I would guess we would have it done somewhere between later Friday and the middle of next week.
No apologies needed. I’m glad we could discover this for you. The timeframe for the backfill is completely reasonable and the fact that new vector stores are now working is great! Thank you very much.
It seems that the only thing left now is correcting where some vector stores are not displaying their association with their respective assistants.
@zbrunson can you check again? This is happening again right now via both API and platform.openai.com - I can create them but not list them.
We are experiencing some system issues right now (https://status.openai.com/). I am seeing success with listing vector stores, but have indications that there may be some issues with this part of the system. I’m working with the team to resolve this.
@zbrunson the issues on the status page are for sora…
Just try making a vector and it won’t list it back. This is super important for my app!
The status page was showing an API issue earlier, but this did not get fixed along with the broader issue. I have a reproduction internally and am working with the team to resolve the issue.
The team resolved this yesterday evening, please let me know if you experience more issues with it. We have also taken steps to increase our monitoring of this endpoint and should be able to react proactively if there are future issues.
A post was merged into an existing topic: openAI Retrieval Platform intermittent issue
