Missing index on agentCategorySchema prevents app from running against "Azure Cosmos DB for MongoDB"

[mforman]

What happened?

We're running in Azure and using CosmosDB as our Mongo instance.

After pulling an image newer than v0.8.0-rc2 the app fails to start.

I've confirmed locally that the missing index is on agentCategorySchema

Version Information

ghcr.io/danny-avila/librechat latest 5c2f6344ebbe 7 days ago 2.75GB

Steps to Reproduce

1. Use Cosmos DB instead of MongoDB container or Atlas database.
2. Get error immediately following successful login

What browsers are you seeing the problem on?

No response

Relevant log output

error: There was an uncaught error: Error=2, Details='Response status code does not indicate success: BadRequest (400); Substatus: 0; ActivityId: b4246c6b-1591-40aa-b034-9b5d7250f084; Reason: (Message: {"Errors":["The order by query does not have a corresponding composite index that it can be served from."]}
ActivityId: b4246c6b-1591-40aa-b034-9b5d7250f084, Request URI: /apps/d8849f9f-bf2f-4649-beb5-7518eadc313c/services/08758d1c-d10b-42bd-be18-00a5b7a30800/partitions/ebd3dd8a-b421-4b0e-9ebe-fae2e6f5b7ea/replicas/134012064128086972s/, RequestStats: Microsoft.Azure.Cosmos.Tracing.TraceData.ClientSideRequestStatisticsTraceDatum, SDK: Windows/10.0.20348 cosmos-netstandard-sdk/3.18.0);

Screenshots

No response

Code of Conduct

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

[nitroxeno]

Same issue here. Creating the index manually got me past the container crash:
db.agentcategories.createIndex({ order: 1, label: 1 })

However, I hit another roadblock when trying to access existing agents in the agent builder:
{"level":"error","message":"[PermissionService.findPubliclyAccessibleResources] Error: $bitsAllSet not supported","timestamp":"2025-08-28T21:20:20.825Z"} I checked my MongoRequests and see the following query being sent and returning error code 115: {"request":"{ "distinct" : "aclentries", "key" : "resourceId", "query" : { "$or" : [{ "principalType" : "user", "principalId" : ObjectId("67d9ec2cef507d0a3c3083bf") }, { "principalType" : "role", "principalId" : "ADMIN" }, { "principalType" : "public" }], "resourceType" : "agent", "permBits" : { "$bitsAllSet" : 2 } }, "lsid" : { "id" : CSUUID("22ef8cc0-714e-43d6-bfa7-64873107ab59") }, "$db" : "LibreChat" }"}

I suspect moving from the RU to the vCore deployment model would fix it, unfortunately that is not an option for me in my Azure region.