App-level auto-destroy timeout
Chatrooms are automatically destroyed by default. If no messages are sent and no members join a chatroom within a specified period (1 hour by default), the RC server will remove all members and destroy the chatroom. You can customize the timeout period from 1 to 24 hours.
When a chatroom is destroyed, a notification is sent to its members, allowing the client app to handle this event (this is dependent on the SDK version).
Each chatroom has a sessionId that is constant for its lifetime. A new sessionId is generated when the chatroom is recreated. This helps clients differentiate between sessions if the same chatroom ID is reused.
You can configure the app-level timeout on the Basic Features page in the Console by setting the Chatroom auto-destroy timeout.
Chatroom-specific settings
In addition to the app-level setting, you can also configure the auto-destroy behavior for specific chatrooms.
-
You can set the Auto-destroy type to either Destroy after inactivity or Destroy at a fixed time. The duration can be extended from the default of 1 hour up to 7 days.
- Related documentation:
Set Chatroom Auto-Destruction Type
- Related documentation:
-
To keep a chatroom alive permanently, you have two options:
- Option 1: Enable the Chatroom Keepalive feature. You can set up to 5 chatrooms for keep-alive. Contact our sales team if you need more.
- Related documentation:
Chatroom Keepalive
- Related documentation:
- Option 2: Keep the chatroom active by periodically sending messages to it (no limit on the number of chatrooms). You can send a message at an interval shorter than the inactivity timeout. To avoid displaying these keep-alive messages to users, you can use custom messages and have the client app filter them out.
- Option 1: Enable the Chatroom Keepalive feature. You can set up to 5 chatrooms for keep-alive. Contact our sales team if you need more.
If you have any questions about this feature, feel free to submit a ticket to us.