Vector stores not being attached assistants when creating threads

API Bugs
, , ,
1

Anyone else having issues when creating threads with attached vector stores? This started happening a couple of days ago and I’ve not had much success since.

Feeding in vector store IDs when creating threads should attach the vector store allowing the assistant to search.

For reference the request body:

{
    "assistant_id":"asst_xxx",
    "max_completion_tokens":4096,
    "thread":{
        "messages":[
            {
                "role":"user",
                "content":"Identify which file is most likely to be a quote and then extract quote information. Use the following files: file-xxx"
            }
        ]
    },
    "tool_choice":{
        "type":"file_search"
    },
    "tool_resources":{
        "file_search":{
            "vector_store_ids":[
                "vs_xxxx"
            ]
        }
    },
    "response_format":{
        "type":"json_object"
    }
}

as I say this used to work we’ve not changed anything our end. I can see the vector store with a single file in but it ends up not being attached in the UI:

image
image1342×380 5.72 KB

I can see in the thread run it says it has the tool resource available but it seems unable to search it:

"tool_resources": {
  "file_search": {
    "vector_store_ids": [
      "vs_690b229286cc8191867f82c826ebb3f9"
    ]
  }
},
1 Like
2

The “used by” UI endpoint was completely broken for a week. I would not rely on that for truth.

The most important metric to look at is the input token count, and then analysis of steps to see the parts included from a vector store and their scores. You can see if the vector store is even being furnished.

Assistants not getting data retrieval from vector stores has been ongoing, including problems with vector store files themselves.

One thing you can do is ensure that all server-side assets are under one project and by one API key, from file upload, vector store creation and file attachment, the assistants and threads and runs inference. Part of what has been recently rolled out (besides problems) is full project scoping (with Assistants compatibility obviously an afterthought). That might mean starting from scratch with a re-creation, ensuring everything is under the project scope of current user “threads”.