Cannot disable retention after enabled

[zuntio]

Description:

Retention cannot be turned off from admin panel after turned on. Confirmed from database using mongosh that settings were indeed not affected when trying to disable retention.

Steps to reproduce:

1. Go to workspace -> Settings -> Retention
2. Turn retention on
3. Save changes
4. Turn retention off
5. Save changes
6. Refresh page

Expected behavior:

Retention should be off. Room infos should not show next purge occurrence

Actual behavior:

Retention is still on and room infos are showing the next purge occurrence

Server Setup Information:

• Version of Rocket.Chat Server: 7.5.0
• License Type: Community
• Number of Users: 46
• Operating System: Ubuntu 24.04
• Deployment Method: snap
• Number of Running Instances: 1
• DB Replicaset Oplog: N/A
• NodeJS Version: 22.13.1
• MongoDB Version: 6.0.19

Client Setup Information

• Desktop App or Browser Version: Chrome 135.0.7049.115 and Firefox 137.0.2
• Operating System: Windows

Additional context

After retention overrides were created for one room, global setting started to comply, so that worked as workaround.

Server instance has existed since Rocket Chat major version 2 and raised up to 7 one version at the time, if it matters.

Relevant logs:

Not unfortunately available due restoration of server backup after faulty setup.

[Gummikavalier]

I cannot reproduce this at least in RC 7.6.0-rc.2 and RC 7.5.1. The channels top pruning notifications messages change/disappear immediately when I save retention policy settings, and the change remains as it should after refreshing too. Also the change is correctly visible on channels top message.

I tested with both admin Retention policy enabled and disabled, as well as its sub Global Policy settings public/private/direct rooms.

If you log into RC as an admin in a private/incognito browser window to completely clear up the browser cache, does the issue still happen for you?

I've seen this kind of admin settings issues pretty often on our instances. Sometimes shift-reload helps for it, but some times I've had to logoff from the admin session, absolutely clear up everything under browser F12 -> Storage/Application while on the login page, and then log back in.