This message was deleted.

example event

{
  "event": "participant_joined",
  "room": {
    "sid": "RM_V6R7ReMAybHC",
    "name": "76c10674-9d97-44ce-a9a1-f488a668565f",
    "empty_timeout": 300,
    "creation_time": 1683813345,
    "turn_password": "i8jxtUiex01bJ1xVB7Gv5H5OD5k=",
    "enabled_codecs": [
      {
        "mime": "audio/opus"
      },
      {
        "mime": "audio/red"
      },
      {
        "mime": "video/VP8"
      },
      {
        "mime": "video/H264"
      }
    ]
  },
  "participant": {
    "sid": "PA_HZhWkjhmdndJ",
    "identity": "f8c82faa-0fe4-4f6d-ac66-eefc4c7215e6",
    "state": 2,
    "metadata": "{.. OK ..}",
    "joined_at": 1683814330,
    "name": "sharmila3",
    "version": 2,
    "permission": {
      "can_subscribe": true,
      "can_publish": true,
      "can_publish_data": true
    },
    "region": "lapsoutha"
  },
  "id": "EV_AsaQYaSF9FzG",
  "created_at": 1683814332
}

It should be sent if room metadata is known at the point of the participant joining. are you seeing this getting dropped at some point?

not sure, but this can be, when we are testing and trying to join the same room post room-ended callback is received. order of events 1. trigger create room api from backend 2. user A joins 3. user B joins 4. both leave, room ended is received 5. not triggering create room 6. user A again joins the same room a. participant_joined is received first, then room_started is received. 7. user A leaves a. participant_left is received b. this is also missing the room metadata