Session inconsistency - requested room does not exist

Cloud Dashboard
1

Hi, recently we are experiencing an increased number of issues in sessions inconsistency which affects recording and session management.

Here is an example (all times in UTC):

SessionId: RM_vpSBCRaAoTKM
RoomId: 1029397-5c008ddb40594c36b9f1e22d0bff75ad
In sessions dashboard it states that it was started 2nd June 2:35:15 PM and finished 2nd June 2:35:22 - but when navigating to details there is a real session time 2:35:15 - 4:17:08. Furthermore API returns 404 when we call any action related to this room - recording attempts and metadata updates.

Room recording error: Not Found: requested room does not exist (2:40:25 PM)
Failed to update room metadata: Not Found: requested room does not exist (3:33:36 PM)

Previous example:
SessionId: RM_bRdCiSsXQ9xu
RoomId: 532790-fa4fcc9a1c8249ec89cabd142de6c205

Here there is no discrepancy in between sessions dashboard and session details but we received 404 as well on recording attempts and metadata updates.

2

Hi Marek,

If you look at the session events for those two rooms:

And go to the final page which shows the earliest events, you’ll see that in both cases the room was created, then deleted, then participants join that room shortly after. I think this is the source of the confusion.

The most common cause of this is re-use of room names, I would recommend using unique room names where possible (I had some other advice in this answer)

Also, just to clarify on some of the naming convention, what you classify as a ‘RoomId’ is actually a ‘Room name’, multiple rooms can have the same name (but the room session ID must be unique). Personally, I tend to get lazy and will sometimes refer to a session ID as a room ID.