Can't open channel settings because of an exception in msToTimeUnit (invalid timespan)

[MarcoSteinacher]

Description:

When I try to edit the channel settings, an error is displayed. The reason seems to be an invalid timespan in msToTimeUnit. It happens on our new Rocket.Chat 8.7.0 installation and all the channels are affected.

Steps to reproduce:

1. Go to an existing channel.
2. Open the channel info sidebar.
3. Click on Edit (pencil icon).
4. Instead of the settings form the error "Something went wrong" is displayed.

Expected behavior:

The channel settings form should appear so the settings can be changed.

Actual behavior:

An error is displayed and the console shows:

So there seems to be a problem with msToTimeUnit (invalid timespan) in convertTimeUnit.ts, used by EditRoomInfo.tsx.

Server Setup Information:

• Version of Rocket.Chat Server: 8.7.0
• License Type: Community
• Number of Users: 2
• Operating System: Linux
• Deployment Method: Docker
• Number of Running Instances: 1
• DB Replicaset Oplog:
• NodeJS Version: v22.22.3
• MongoDB Version: 8.0.28

Client Setup Information

• Desktop App or Browser Version: Chromium 151.0.7922.71 and Firefox 140.13.0esr
• Operating System: Debian GNU/Linux 12

Relevant logs:

From browser console (see also screenshot above):

Error: msToTimeUnit - invalid timespan:63072000000.0
    o /client/lib/convertTimeUnit.ts:1
    module /client/views/room/contextualBar/Info/EditRoomInfo/EditRoomInfo.tsx:1
    React 15
        l5
        o_
        oq
        iw
        ik
        ik
        ii
        iZ
        iq
        iY
        iW
        iW
        iu
        a5
        a6
    onClickEdit /client/views/room/contextualBar/Info/RoomInfoRouter.tsx:1
    React 11
        i6
        st
        nE
        st
        cd
        cc
        sn
        i9
        se
        se
        createRoot
    module /client/startup/appRoot.tsx:1
    s https://chat.example.com/bb09ac2e5f6f33ebed8513db7fa126a54a92e629.js?meteor_js_resource=true:375
    g https://chat.example.com/bb09ac2e5f6f33ebed8513db7fa126a54a92e629.js?meteor_js_resource=true:5
    require https://chat.example.com/bb09ac2e5f6f33ebed8513db7fa126a54a92e629.js?meteor_js_resource=true:5
    require https://chat.example.com/bb09ac2e5f6f33ebed8513db7fa126a54a92e629.js?meteor_js_resource=true:7
    i https://chat.example.com/bb09ac2e5f6f33ebed8513db7fa126a54a92e629.js?meteor_js_resource=true:7
    module /client/startup/index.ts:1
    s https://chat.example.com/bb09ac2e5f6f33ebed8513db7fa126a54a92e629.js?meteor_js_resource=true:375
    g https://chat.example.com/bb09ac2e5f6f33ebed8513db7fa126a54a92e629.js?meteor_js_resource=true:5
    require https://chat.example.com/bb09ac2e5f6f33ebed8513db7fa126a54a92e629.js?meteor_js_resource=true:5
    require https://chat.example.com/bb09ac2e5f6f33ebed8513db7fa126a54a92e629.js?meteor_js_resource=true:7
    i https://chat.example.com/bb09ac2e5f6f33ebed8513db7fa126a54a92e629.js?meteor_js_resource=true:7
    dynamicImport https://chat.example.com/bb09ac2e5f6f33ebed8513db7fa126a54a92e629.js?meteor_js_resource=true:375
    promise callback*client.js/s.prototype.dynamicImport https://chat.example.com/bb09ac2e5f6f33ebed8513db7fa126a54a92e629.js?meteor_js_resource=true:375
    ts https://chat.example.com/bb09ac2e5f6f33ebed8513db7fa126a54a92e629.js?meteor_js_resource=true:520
    promise callback*main.ts https://chat.example.com/bb09ac2e5f6f33ebed8513db7fa126a54a92e629.js?meteor_js_resource=true:520
    g https://chat.example.com/bb09ac2e5f6f33ebed8513db7fa126a54a92e629.js?meteor_js_resource=true:5
    require https://chat.example.com/bb09ac2e5f6f33ebed8513db7fa126a54a92e629.js?meteor_js_resource=true:5
    require https://chat.example.com/bb09ac2e5f6f33ebed8513db7fa126a54a92e629.js?meteor_js_resource=true:7
    n https://chat.example.com/bb09ac2e5f6f33ebed8513db7fa126a54a92e629.js?meteor_js_resource=true:5
    <anonymous> https://chat.example.com/bb09ac2e5f6f33ebed8513db7fa126a54a92e629.js?meteor_js_resource=true:520
/node_modules/react-dom/cjs/react-dom-client.production.js:1:68112
    React 200
        od
        oh
        callback
        lF
        lD
        o3
        ui
        uk
        ui
        uk
        ui
        uk
        ui
        [...]

[MarcoSteinacher]

Update: The issue seems to be related to the global prune (RetentionPolicy) settings. I could fix the problem by resetting all prune settings to the defaults and then set it to the same custom settings again in the workspace admin UI.

The custom settings were initially set by the following Docker environment variables:

OVERWRITE_SETTING_RetentionPolicy_Enabled="True" # default: False
OVERWRITE_SETTING_RetentionPolicy_Precision="3" # default: 0
OVERWRITE_SETTING_RetentionPolicy_AppliesToChannels="True" # default: False
OVERWRITE_SETTING_RetentionPolicy_AppliesToDMs="True" # default: False
OVERWRITE_SETTING_RetentionPolicy_AppliesToGroups="True" # default: False
OVERWRITE_SETTING_RetentionPolicy_DoNotPrunePinned="True" # default: False
OVERWRITE_SETTING_RetentionPolicy_FilesOnly="True" # default: False
OVERWRITE_SETTING_RetentionPolicy_MaxAge_Channels="-1" # default: 30
OVERWRITE_SETTING_RetentionPolicy_MaxAge_DMs="-1" # default: 30
OVERWRITE_SETTING_RetentionPolicy_MaxAge_Groups="-1" # default: 30
OVERWRITE_SETTING_RetentionPolicy_TTL_Channels="63072000000.0" # default: 2592000000.0
OVERWRITE_SETTING_RetentionPolicy_TTL_DMs="31536000000.0" # default: 2592000000.0
OVERWRITE_SETTING_RetentionPolicy_TTL_Groups="63072000000.0" # default: 2592000000.0

So this might point to an inconsistency between the TTL values from Docker env variables and values entered through the UI. Maybe the TTL values in the Docker env also need to be days and not milliseconds, even though the settings seem to be stored in milliseconds in the database? However, the Docker settings above have worked, because the correct values in days were in the UI before I did the reset to fix the issue: