** @(CHA-RL5d)@ Once all channels (except the channel that entered @SUSPENDED@, per @CHA-RL5a@) have been detached, the room waits until the original channel that caused the retry loop naturally enters the @ATTACHED@ state. This is handled by the underlying Realtime SDK.
It’s possible that the triggering contributor entered ATTACHED / FAILED during CHA-RL5b’s detach. So we presumably also want to check whether the channel is already in such a state? (And then the language in CHA-RL5e and CHA-RL5f should be updated to match.)
It’s possible that the triggering contributor entered ATTACHED / FAILED during CHA-RL5b’s detach. So we presumably also want to check whether the channel is already in such a state? (And then the language in CHA-RL5e and CHA-RL5f should be updated to match.)