This still occurs in my current flatpak version:
Stable Desktop 2026.1105.11444
Web 2026.1107.204546
Linux 7.3.3-1-cachyos (x64)
Electron 44.10.0
Chrome 152.0.7977.169
Node 24.22.1
Locale en-US
Observed behavior:
User joins a channel and connects to voice.
An admin moves the user to another channel.
Instead of being auto-connected in the new channel, the user is prompted to connect voice.
Following this, the user is briefly presented with a reconnect prompt and gets placed back in the previous channel with voice connected.
My interpretation of the events:
The sequence looks like the move is treated as a sudden disconnect, which appears to trigger an auto-reconnect feature (if it exists) that restores the last connected channel. If so, that feature makes sense for genuine sudden disconnects but should not fire on an intentional move. A moved use that was voice-connected in the previous channel and moved should be voice-connected in the destination channel they get moved to.
Thread
Comment by Rex
Comment by Aidan
Comment by Excorio
- User joins a channel and connects to voice.
- An admin moves the user to another channel.
- Instead of being auto-connected in the new channel, the user is prompted to connect voice.
- Following this, the user is briefly presented with a reconnect prompt and gets placed back in the previous channel with voice connected.
My interpretation of the events: The sequence looks like the move is treated as a sudden disconnect, which appears to trigger an auto-reconnect feature (if it exists) that restores the last connected channel. If so, that feature makes sense for genuine sudden disconnects but should not fire on an intentional move. A moved use that was voice-connected in the previous channel and moved should be voice-connected in the destination channel they get moved to.