Files deleted in agents' file search section not disappearing from UI

[mansiibm]

What happened?

Whenever I upload a file to agents in the file search capability, the file is reflected as it is. If I remove the file and save the agent, the file does not go away from the UI, it stays by the name document.

Although when file is removed/deleted it shows in the backend-

This agent was made on azure openai using gpt-4o-mini model and is personal not shared.

Version Information

Using the latest tag - ghcr.io/danny-avila/librechat-dev-api:fdb3cf3f583c63c7bef67c267878d61eeec0553e. Hosted LC as container in the azure portal.
rag version being used: danny-avila/librechat-rag-api-dev:9e4bb52e15d97856e3b69653c88d2cf1bb34324f

Steps to Reproduce

1. Enable file search
2. Upload a file and save
3. Click on the cross button on the file
4. The file goes away
5. Reload the page
6. The file appears as again by the name document

What browsers are you seeing the problem on?

Microsoft Edge

Relevant log output

Screenshots

file.from.UI.mp4

Code of Conduct

• I agree to follow this project's Code of Conduct

[danny-avila]

Following the steps, I can't reproduce this on latest image. There is also something weird happening in your video where File Search is getting toggled off as soon as the file finishes uploading. That could be part of the issue, but I could not reproduce it.

[mansiibm]

Hi Danny thanks for replying, I am re-submitting a video. In the local everything is fine only in azure this happens.

re-submit.mp4

[mansiibm]

In the logs from UI - Failed to load resource: the server responded with a status of 404 ()

[mansiibm]

Hi Danny, wanted to share the following observations with you with the version- ghcr.io/danny-avila/librechat-dev-api:ecddffa7b241502c0a4342f4b1c1c65467e754dd

1. I create an agent with the name - mg-5 , at the time of creation I have not uploaded any files to it.

2. Now when I upload a file it appears with agents config also -

3. Now if I delete the files - 2 files section appear-

4. With a reponse-

5. But the agent's status after the second file - not modified

and the files exist after deletion.

5. And in the UI- file appears as - document.

6. And in the database no file is present

7. But the file_id in the agents section in the database exists even when it is deleted from the UI.

{
"_id" : ObjectId("67bc016da837e4c943bee348"),
"id" : "agent_lBHrixTFOOodFjAS-UsM6",
"name" : "mg-5",
"description" : "",
"instructions" : "",
"provider" : "azureOpenAI",
"model" : "gpt-4o",
"artifacts" : "",
"tools" : [
"file_search"
],
"tool_kwargs" : [ ],
"author" : ObjectId("66e2c6cd3f662eed93695bac"),
"agent_ids" : [ ],
"conversation_starters" : [ ],
"projectIds" : [ ],
"createdAt" : {
"$date" : 1740374381229
},
"updatedAt" : {
"$date" : 1740374434306
},
"__v" : 0,
"tool_resources" : {
"file_search" : {
"file_ids" : [
"34c8d512-69c0-4730-9242-b1b662823e58"
]
}
},
"hide_sequential_outputs" : false,
"end_after_tools" : false
}
8. If I am manually deleting the file id form the db then from ui it is going away-

Seems, the deleted file is not getting updated in agent's files record in mongodb.

[ppatayane]

@danny-avila 1 behavior our team was able to pinpoint is :

1. For our existing infra setup (cosmos db, rag etc.) if we use version 0.7.6, file delete has no issues. If we update to tags 0.7.7 RC1 or later (even after the fix for file delete for ex. librechat-dev-api:ecddffa7b241502c0a4342f4b1c1c65467e754dd), it does not work.
2. It only causes the issue for emptying the file list. For ex. If we have 3 files attached to agent, we try to delete 2, it works. If we delete all, it does not update in UI (it deletes in backend). So issue happens when we want to delete ALL files from agent.

[danny-avila]

Are you using Azure Cosmos DB?

[mansiibm]

Yes

[danny-avila]

That's the issue, it seems to be an incompatibility issue, are you using CosmosDB with vCore or RU? I have not heard of any issues when using vCore.

https://learn.microsoft.com/en-us/azure/cosmos-db/mongodb/choose-model

[ppatayane]

@danny-avila Thank you so much for the pointer.
RU - does not work for remove call specifically..
Vcore - works

We tried some config with RU and finally here is the error:
The query that runs according to our cosmos MongoDB (RU) instance is:
{"request":"{ "findAndModify" : "agents", "query" : { "id" : "agent_XA7fxI2z-l66INI0GkjNt" }, "remove" : false, "new" : true, "upsert" : false, "update" : [{ "$set" : { "tool_resources.file_search.file_ids" : { "$filter" : { "input" : "$tool_resources.file_search.file_ids", "cond" : { "$not" : [{ "$in" : ["$$this", ["f536226f-2c56-468e-82aa-29b214ab667c"]] }] } } } } }, { "$set" : { "tool_resources.file_search" : { "$cond" : [{ "$eq" : ["$tool_resources.file_search.file_ids", []] }, "$$REMOVE", "$tool_resources.file_search"] } } }, { "$set" : { "updatedAt" : ISODate("2025-03-05T14:02:01.584Z") } }], "lsid" : { "id" : CSUUID("288e7110-5f5e-453e-890c-4c24848a6285") }, "$db" : "test" }"}

Error code: 17276

On searching the internet I found: Prisma Client: mongodb-azure-cosmosdb client.user.create() fails with Command failed (17276): Use of undefined variable: REMOVE) · Issue #15083 · prisma/prisma similar issues with $$REMOVE command.

As per my previous screenshot in my earlier comment LibreChat moved to this $$REMOVE logic which seems to not work in RU instances but works in vCore. Although Microsoft says in RU $$REMOVE is supported as per their documentation but it seems it has issues and several people have reported it.

The change that happened after version 0.7.6 as highlighted below, which is not supported by RU :

Question : May I ask, was there any specific reason for this highlighted update(remove call)? Is it possible to revert above changes as before?

If it is possible for you to make this in any other way or as previous, this would work for us too. If by any means you confirm it won't be possible, we can check for migration of DB from RU to Vcore..

[ppatayane]

We tried this with Vcore and it works. We will migrate to this as recommended. Thanks everyone.

[petracvv]

For everyone here, it looks like AWS DocumentDB also does not implement the $$REMOVE variable. See their docs
We ran into this issue as well after updating to 0.7.7

[danny-avila]

Thanks for letting me know, will have to try it myself on DocumentDB

[danny-avila]

Fully closed by #6726