LiveKit Community

Thanks for the report. which fields are you updating for the participannt?

<@U01KZ61GV5Z> after further into the this investigation, dev team confirm that the issue is with to server-sdk-js  &gt;  <https://github.com/livekit/server-sdk-js/releases/tag/v1.1.0> -  v1.1.0.
Let us know if you need further request and response for follow up.

<@U045CJPACG1> I'm  unable to reproduce this on my end. Could you include a room and participant that you tried to update? we can check the logs on our end.

<@U01KZ61GV5Z> the issue is related to <https://livekit-users.slack.com/archives/C01KZ61HZRR/p1669695209223889> msg.
```    data: '{"room":"TestMe-ep4ed-vxk3r-sz569","metadata":"{\\"role\\":\\"admin\\",\\"endCallback\\":\\"https//www.****.com\\",\\"whiteboardAccess\\":true,\\"isRoomBlocked\\":true,\\"isWaitingRoomEnabled\\":false}"}',```
With above request, we are adding our own custom metadata &gt; attributes as well to keep the user states.

<@U01KZ61GV5Z> just quick thought, in the metadata are you guys using `endCallback` as reserved key attribute ?

nope, we are not. it's a opaque field that we do not touch

we are investigating an issue with `updateRoomMetadata` with Cloud. it does seem to fail sometimes.

Aha ok, thanks for the confirmation. Kindly confirm once the issue is sorted

will do. currently it would sometimes return 500 even when the request has gone through successfully. we'll be fixing this shortly.