Latest build has agent error: "error: Failed to check agent permissions migration invalid $lookup namespace"

[zeemy23]

What happened?

error: Failed to check agent permissions migration invalid $lookup namespace

Version Information

a6fd32a

Steps to Reproduce

1. upgrade to a6fd32a
2. log for error: Failed to check agent permissions migration invalid $lookup namespace

What browsers are you seeing the problem on?

Microsoft Edge

Relevant log output

error: Failed to check agent permissions migration invalid $lookup namespace

Screenshots

No response

Code of Conduct

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

[danny-avila]

There's not enough information as the issue can't be reproduced.

Are you using MongoDB or a drop-in replacement (CosmosDB, DocumentDB, FerretDB, etc.)?

How are you running LibreChat? Using npm directly or docker? How are you updating?

Can you provide more logs before and after the one you are observing?

Can you provide error-specific logs which provide stack traces?

Log locations:

• Docker: Project root directory ./logs
• npm: ./api/logs

There are two types of logs that can help diagnose the issue:

• debug logs (debug-YYYY-MM-DD.log)
• error logs (error-YYYY-MM-DD.log)

Error logs contain exact stack traces and are especially helpful, but both can provide valuable information.

Please only include the relevant portions of logs that correspond to when you reproduced the error.

[zeemy23]

sorry, its actually aws documentDB, not mongodb

[zeemy23]

@danny-avila sorry to bother, just wanted to let you know that this appears to be a documentDB issue related to the migration checks.

[apdsdoug]

@zeemy23 were you able to fix the issue with documentDB or did you just revert versions?

[zeemy23]

i just reverted for now

[danny-avila]

I know of people using DocumentDB not having this issue, will check with them to see.

[danny-avila]

Is the error blocking your use of the app? The log error "Failed to check agent permissions" is not a blocking error, it just fails to check if any of your agents are requiring migration, which is to issue a warning/instructions on how to migrate.

To run the same script as the check, you run npm run migrate:agent-permissions:dry-run

and then npm run migrate:agent-permissions to actually perform the migration.

You would run this script according to your setup as you would other scripts:
https://www.librechat.ai/docs/configuration/authentication#create-user-script

[apdsdoug]

I am getting the same invalid $lookup namespace error after correcting my config location, and I am also using DocumentDB:

/app # npm run migrate:agent-permissions:dry-run

> [email protected] migrate:agent-permissions:dry-run
> node config/migrate-agent-permissions.js --dry-run

Warming up the engines...
{"level":"info","message":"Mongo Connection options","timestamp":"2025-08-22T19:53:39.031Z"}
{"level":"info","message":"{\n  \"bufferCommands\": false\n}","timestamp":"2025-08-22T19:53:39.032Z"}
{"batchSize":100,"dryRun":true,"level":"info","message":"Starting Enhanced Agent Permissions Migration","timestamp":"2025-08-22T19:53:39.097Z"}
{"level":"info","message":"Found 5 agents in global project","timestamp":"2025-08-22T19:53:39.129Z"}
Enhanced migration failed: MongoServerError: invalid $lookup namespace
    at Connection.sendCommand (/app/node_modules/mongoose/node_modules/mongodb/lib/cmap/connection.js:299:27)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Connection.command (/app/node_modules/mongoose/node_modules/mongodb/lib/cmap/connection.js:327:26)
    at async Server.command (/app/node_modules/mongoose/node_modules/mongodb/lib/sdam/server.js:168:29)
    at async AggregateOperation.executeCommand (/app/node_modules/mongoose/node_modules/mongodb/lib/operations/command.js:76:16)
    at async AggregateOperation.execute (/app/node_modules/mongoose/node_modules/mongodb/lib/operations/aggregate.js:87:16)
    at async tryOperation (/app/node_modules/mongoose/node_modules/mongodb/lib/operations/execute_operation.js:207:20)
    at async executeOperation (/app/node_modules/mongoose/node_modules/mongodb/lib/operations/execute_operation.js:75:16)
    at async AggregationCursor._initialize (/app/node_modules/mongoose/node_modules/mongodb/lib/cursor/aggregation_cursor.js:56:26)
    at async AggregationCursor.cursorInit (/app/node_modules/mongoose/node_modules/mongodb/lib/cursor/abstract_cursor.js:633:27) {
  errorLabelSet: Set(0) {},
  errorResponse: {
    ok: 0,
    operationTime: new Timestamp({ t: 1755892419, i: 1 }),
    code: 40322,
    errmsg: 'invalid $lookup namespace'
  },
  ok: 0,
  operationTime: new Timestamp({ t: 1755892419, i: 1 }),
  code: 40322
}

[apdsdoug]

The issue is that aclentries doesn't exist. After creating the collection with db.createCollection('aclentries'); I can successfully run the migration script. @zeemy23 FYI this will probably fix your issue!

accessroles
agentcategories
agents
conversations
conversationtags
files
memoryentries
messages
pluginauths
projects
promptgroups
prompts
roles
sessions
sharedlinks
transactions
users

Migration Results: {
  "migrated": 20,
  "errors": 0,
  "publicViewGrants": 3,
  "publicEditGrants": 2,
  "ownerGrants": 20
}

[zeemy23]

awesome thanks!

[danny-avila]

Thanks @apdsdoug it is unusual that the collection is not getting created as it gets created the same time as all other collections if non-existent.

Only thing I can think of is DocDB not liking something in the schema for this collection, may need to test it further.

[danny-avila]

Once this is merged, collection creation should be automated, since it seems DocDB has different behavior on collection creation timing than MongoDB

#9249