twilio-video.js icon indicating copy to clipboard operation
twilio-video.js copied to clipboard

Twilio Error: Room not found

Open michalzaq12 opened this issue 3 years ago • 5 comments

Hi, many users get Room not found error Could you please help with further investigation?

Room options:

type: 'go',
emptyRoomTimeout: 1,
unusedRoomTimeout: 1,

Some client logs:

15:49:26 Connected
15:54:51.043 warn [PeerConnectionV2 #3: 35746452-cfdd-4c44-81d3-7d8c0a23dee8] ICE Connection Monitor detected inactivity
15:54:51.046 warn [PeerConnectionV2 #3: 35746452-cfdd-4c44-81d3-7d8c0a23dee8] An ICE restart has been scheduled
15:54:51.052 warn [PeerConnectionV2 #3: 35746452-cfdd-4c44-81d3-7d8c0a23dee8] Attempting to restart ICE
15:54:57.688 Ably: Transport.onIdleTimerExpire(): No activity seen from realtime in 15109ms; assuming connection has dropped
15:54:59.508 warn [TwilioConnection #2: wss://global.vss.twilio.com/signaling] Closing: 3001 - Missed 3 "heartbeat" messages
15:54:59.510 warn [TwilioConnection #2: wss://global.vss.twilio.com/signaling] Closed: 3001 - Missed 3 "heartbeat" messages
15:54:59.512 error [connect #2] event [object Object]
15:55:47.606 warn [TwilioConnection #3: wss://global.vss.twilio.com/signaling] Closing: 3001 - Missed 3 "heartbeat" messages
15:55:47.611 warn [TwilioConnection #3: wss://global.vss.twilio.com/signaling] Closed: 3001 - Missed 3 "heartbeat" messages
15:55:47.618 error [connect #2] event [object Object]
15:55:52.915 Ably: Transport.onIdleTimerExpire(): No activity seen from realtime in 15104ms; assuming connection has dropped
16:09:01 Ably: Transport.onIdleTimerExpire(): No activity seen from realtime in 739737ms; assuming connection has dropped
16:09:01.783 warn [TwilioConnection #4: wss://global.vss.twilio.com/signaling] Closing: 3001 - Missed 3 "heartbeat" messages
16:09:01.787 error [connect #2] event [object Object]
16:09:01.789 warn [PeerConnectionV2 #3: 35746452-cfdd-4c44-81d3-7d8c0a23dee8] ICE failed
16:09:01.789 warn [PeerConnectionV2 #3: 35746452-cfdd-4c44-81d3-7d8c0a23dee8] An ICE restart has been scheduled
16:09:01.857 warn [PeerConnectionV2 #3: 35746452-cfdd-4c44-81d3-7d8c0a23dee8] Attempting to restart ICE
16:09:02 TwilioError: Room not found

----------

20:21:49 Connected
20:27:03.424 warn [TwilioConnection #1: wss://global.vss.twilio.com/signaling] Closing: 3001 - Missed 3 "heartbeat" messages
20:27:03.441 warn [TwilioConnection #1: wss://global.vss.twilio.com/signaling] Closed: 3001 - Missed 3 "heartbeat" messages
20:27:03.486 error [connect #1] event [object Object]
20:27:06 TwilioError: Room not found

---------

11:32:27 Connected
11:35:08.728 warn [TwilioConnection #1: wss://global.vss.twilio.com/signaling] Closing: 3001 - Missed 3 "heartbeat" messages
11:35:08.729 warn [TwilioConnection #1: wss://global.vss.twilio.com/signaling] Closed: 3001 - Missed 3 "heartbeat" messages
11:35:08.731 error [connect #1] event [object Object]
11:35:08.732 Ably: Transport.onIdleTimerExpire(): No activity seen from realtime in 75772ms; assuming connection has dropped
11:35:09 TwilioError: Room not found

-----
01:53:07 Connected
02:34:35.441 warn [TwilioConnection #1: wss://global.vss.twilio.com/signaling] Closed: 1006 
02:35:11.542 error [connect #1] event [object Object]
02:35:13 TwilioError: Room not found

---
17:12:15 Connected
17:15:04.512 warn [TwilioConnection #1: wss://global.vss.twilio.com/signaling] Closed: 1011 - 3 heartbeats missed. Closing connection
17:15:04.532 error [connect #1] event [object Object]
17:15:28 TwilioError: Room not found

---
22:48:28 Connected
22:55:21.105 warn [TwilioConnection #1: wss://global.vss.twilio.com/signaling] Closed: 1011 - 3 heartbeats missed. Closing connection
22:55:21.113 error [connect #1] event [object Object]
22:55:22 TwilioError 53106: Room not found


---
05:08:03 Connected
05:10:42.555 warn [TwilioConnection #1: wss://global.vss.twilio.com/signaling] Closed: 1006 
05:11:30.997 error [connect #1] event [object Object]
05:11:33.014 warn [TwilioConnection #2: wss://global.vss.twilio.com/signaling] Closed: 1006
05:11:33.015 error [connect #1] event [object Object]
05:11:33.193 warn [TwilioConnection #3: wss://global.vss.twilio.com/signaling] Closed: 1006
05:11:33.194 error [connect #1] event [object Object]
05:11:33.435 warn [TwilioConnection #4: wss://global.vss.twilio.com/signaling] Closed: 1006
05:11:33.435 error [connect #1] event [object Object]
05:11:33.754 warn [TwilioConnection #5: wss://global.vss.twilio.com/signaling] Closed: 1006
05:11:33.754 error [connect #1] event [object Object]
05:11:34.275 warn [TwilioConnection #6: wss://global.vss.twilio.com/signaling] Closed: 1006
05:11:34.275Z error [connect #1] event [object Object]
05:11:39 TwilioError 53106: Room not found

michalzaq12 avatar Jun 07 '22 10:06 michalzaq12

Hi @michalzaq12 , thanks for reaching out. I'm not sure what is being asked. Are you asking how many of your users are getting this error, or are you asking why is this error happening? Can you please elaborate more?

Thank you, Charlie

charliesantos avatar Jun 07 '22 20:06 charliesantos

I would like to know what causes this error and how to prevent it

michalzaq12 avatar Jun 07 '22 20:06 michalzaq12

@michalzaq12 this error usually happens if the client cannot establish a connection to Twilio servers due to network issues. I don't think you can entirely prevent this due to varying network conditions at the time of the call, but you can do some things to handle this when the error happens. For example, you can detect it and notify the user of a network issue, or ask them to check if they have internet and such. Please check our best practice page for proper handling of reconnecting events. https://www.twilio.com/docs/video/reconnection-states-and-events

charliesantos avatar Jun 07 '22 20:06 charliesantos

@charliesantos thanks for the detailed reply. How long does the Twilio SDK try to reconnect? Can this time be configured?

michalzaq12 avatar Jun 10 '22 07:06 michalzaq12

Is there any fix or workaround for this issue?

sundardsTechMind avatar Jun 19 '22 11:06 sundardsTechMind

@michalzaq12 , @sundardsTechMind ,

This error is raised when you are trying to join a Room that does not exist. If you are using the REST API to create Rooms, make sure people join the Room only after it is created. Otherwise, make sure ad hoc Room creation is enabled in your Twilio console so that when you join a Room that does not exist, it is created automatically.

manjeshbhargav avatar Aug 24 '22 18:08 manjeshbhargav

@manjeshbhargav this happens very randomly and rarely, but it happens. In Twilio console I've checked that roomId was created successfully. But still got the error "Error connecting to room: TwilioError 53106: Room not found".

The problem is that it's really hard to reproduce the next time. It works as expected most of the time, but throws this error randomly once in 50 times.

gurgenhakobyan avatar Nov 10 '23 18:11 gurgenhakobyan

I've found out that the problem is that the room immediately gets completed. Any ideas why it happens randomly?

image

gurgenhakobyan avatar Nov 10 '23 20:11 gurgenhakobyan