This message was deleted.

Hey @ancient-cpu-94526, that's helpful to know! In that case, I think this would be the expected behavior for that API. In the perspective of the receiving participant, metadata was in its initial state and had not changed. (since it came down as part of the join response)

(should have mentioned, we discussed on a call)