Deleted file remains in Assistant API response, causing “No such File object” error on update

API Bugs
, ,
1

Hi everyone :waving_hand:,

I’ve encountered a blocking issue when managing files within a Vector Store linked to an Assistant.

I’m creating a VectorStore and uploading files to it via the API. When I delete a file from the Vector Store, it is successfully removed (the DELETE call returns 200), and the file is no longer present in the Vector Store. However, when I call GET /assistants/${assistant_id}, the deleted file still appears in the response under the files array.

When I try to update the Assistant after deleting that file, the API returns:
400 Bad Request: No such File object: file-xxxx

As a result, it becomes impossible to update the Assistant after a file deletion.

After deleting a file from a Vector Store, the deleted file should no longer appear in the Assistant’s file_ids property returned by GET /assistants/{assistant_id}.

This issue is blocking many of our users who rely on the Assistants API for dynamic file management.

Thanks a lot for your help and for looking into this.

Vector Store association endpoint error
2

Hi @milad85 – thanks for reporting, we’re working on this!

2 Likes
3

Hi everyone, thanks for your patience. There was a brief period in which we were not deleting files correctly files for a few impacted vector stores. We fixed this on Nov 5 and deleted the relevant files. If you're still seeing any stuck deleted files, you can delete the empty vector stores to get rid of the files.

Let us know if you have any questions!

1 Like