Agent permissions disappear from UI after saving

[apdsdoug]

What happened?

I tried searching for this issue and wasn't finding it, sorry if it already exists and my searching is just terrible.

New agent permissions are great, however they disappear the next time I go in to edit them. It does seem like people I share with still have access, I just can't see the permissions in the sharing window anymore.

Version Information

[LibreChat v0.8.0-rc3]

I am running this in AWS ECS Fargate, and using DocumentDB for the database.

Steps to Reproduce

1. Create an agent
2. Click share button
3. Add various permissions/users/etc
4. Save permissions
5. Save agent
6. Click share button again
7. All permissions appear gone

What browsers are you seeing the problem on?

Chrome

Relevant log output

I actually don't see anything in browser console logs when saving and reopening agent permissions.

I also don't see any server logs during the same time frame even with debugging turned on.

Screenshots

I made a gif here: https://drive.google.com/file/d/1wgIHXhMTjqBp8yATptPIqVKlGyt20m04/view?usp=sharing

Code of Conduct

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

[apdsdoug]

Noting that this could be related to the fix I did to get the migration script running for my DocumentDB (manually created the aclentries table)
#9130

[danny-avila]

I ran the steps, albeit not on AWS ECS Fargate, and not using DocumentDB for the database, and could not reproduce, so I moved to troubleshooting discussion.

If you can record a video of the exact actions, it would help to determine what you're experiencing.

4. Save permissions
5. Save agent

Note, saving permissions does not directly affect the agent data and vice versa, so these can be understood as isolated operations that should not affect each other (besides deleting an agent, then all tied permissions should be removed).

[danny-avila]

Sorry, just saw that you attached a GIF, it's odd that there are no permissions to begin with as a "created" agent should always have at least one owner to begin with.

Noting that this could be related to the fix I did to get the migration script running for my DocumentDB (manually created the aclentries table)

Maybe if this is an existing agent, but from write-up, you said this is a new one, will take a deeper look here.

[apdsdoug]

Ah yeah the behavior is the same for new agents and for agents that existed before the migration. Thanks for taking a look, let me know if I can provide anything else that would be helpful!

[danny-avila]

This was resolved earlier last week

[gloorung]

I'm having the same issue. On an Azure VM, it works as expected, however, on AWS, it doesn't visualise the previously set permissions. The table in the DocumentDB is correctly updated and the permission are also applied, though visualising previously set permission result in an empty list. I noticed that when making the api call /api/persmissions/agent/, the AWS deployment return an empty array for the principals, whereas on the Azure VM deployment, the values are correct.

Could you share some information on how this can be resolved ?

[gloorung]

I investigated this further and the issue seemed to be caused by the fact the our DocumentDB did not have the 'groups' collections. Creating this resolved the issue.

[apdsdoug]

Ahh thank you, creating this fixed it for me as well!

db.createCollection("groups")