# Unable to join session. Session ses\_XXX cannot be found. Code: 202

**URL:** <https://openvidu.discourse.group/t/unable-to-join-session-session-ses-xxx-cannot-be-found-code-202/3916>\
**Category:** Issues developing apps\
**Tags:** v2\
**Created:** [April 22, 2022, 2:44pm UTC](https://openvidu.discourse.group/t/unable-to-join-session-session-ses-xxx-cannot-be-found-code-202/3916 "2022-04-22T14:44:25Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ale](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@Ale](https://openvidu.discourse.group/u/Ale)\
**Post date:** [April 22, 2022, 2:44pm UTC](https://openvidu.discourse.group/t/unable-to-join-session-session-ses-xxx-cannot-be-found-code-202/3916/1 "2022-04-22T14:44:25Z")

</div>

Hello!  
We are trying out OpenVidu EE but it seems around 50% of the times we fail to `joinRoom` and we get back a `202` error code.  
That doesn’t happen with OpenVidu CE.

At first we thought it’s some race condition where we try to `joinRoom` for a session that is not yet created, but we noticed that:

- Rest APIs confirm the session is created
- Retrying to join the room continues to fail forever (so it is not a race condition)

Example RPC request:

```auto
    {
      "id": 1,
      "jsonrpc": "2.0",
      "method": "joinRoom",
      "params": {
        "metadata": "{ \"clientData\": \"353919813\" }",
        "platform": "Android 30",
        "secret": "",
        "session": "ses_J9rqjRumxi",
        "token": "wss:\/\/myserver.com?sessionId=ses_J9rqjRumxi&token=tok_QHsOHt9gNkdZ5NyD&webrtcStatsInterval=30&sendBrowserLogs=disabled",
        "userId": "353919813"
      }
    }

```

And response:

```auto
    {
      "id": 1,
      "error": {
        "code": 202,
        "message": "Unable to join session. Session ses_J9rqjRumxi cannot be found. Code: 202"
      },
      "jsonrpc": "2.0"
    }

```

Any clue why this happens?

Thank you,  
Alessandro

---

<div class="post-metadata">

**Author:** ![cruizba](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/cruizba/32/18_2.png) [@cruizba](https://openvidu.discourse.group/u/cruizba)\
**Post date:** [April 22, 2022, 4:20pm UTC](https://openvidu.discourse.group/t/unable-to-join-session-session-ses-xxx-cannot-be-found-code-202/3916/2 "2022-04-22T16:20:05Z")

</div>

What OpenVidu EE deployment do you have? Single master or High availability?

---

<div class="post-metadata">

**Author:** ![Ale](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@Ale](https://openvidu.discourse.group/u/Ale)\
**Post date:** [April 26, 2022, 6:08am UTC](https://openvidu.discourse.group/t/unable-to-join-session-session-ses-xxx-cannot-be-found-code-202/3916/3 "2022-04-26T06:08:30Z")

</div>

Hello @cruizba, the OpenVidu EE deployment we have is **High Availability** (2 masters)

---

<div class="post-metadata">

**Author:** ![cruizba](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/cruizba/32/18_2.png) [@cruizba](https://openvidu.discourse.group/u/cruizba)\
**Post date:** [April 27, 2022, 4:21pm UTC](https://openvidu.discourse.group/t/unable-to-join-session-session-ses-xxx-cannot-be-found-code-202/3916/4 "2022-04-27T16:21:51Z")

</div>

Hello @Ale , something is not correctly configured if 50% of the requests are failing. Could we troubleshoot your deployment?

I think @pabloFuente is contacting with you also via email, we can still continue over email.

---

<div class="post-metadata">

**Author:** ![Ale](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@Ale](https://openvidu.discourse.group/u/Ale)\
**Post date:** [April 29, 2022, 9:48am UTC](https://openvidu.discourse.group/t/unable-to-join-session-session-ses-xxx-cannot-be-found-code-202/3916/5 "2022-04-29T09:48:49Z")

</div>

Thanks @cruizba, changing deployment seems to have fixed 🥳 We’ll continue over email! 👋