A number of users, including myself, seem to have been involuntarily added to an internal or deprecated Roblox test program, possibly linked to the now-closed Roblox Beta Program 2021. We didn’t opt in or give permission for this. Affected accounts are being placed into an internal feature channel (zufctesting-flags-on) with channelAssignmentType: 2, which looks like it was assigned through internal tools.
Since being put into this channel, I’ve been seeing the following problems:
- Can’t publish or access public experiences
- Getting placed into solo or self-reserved instances when joining games
- Broken gameplay, like actions only happening on the client (no server-side replication or visibility)
How to Reproduce (for affected accounts):
- Log into an account assigned to the
zufctesting-flags-onchannel (channelAssignmentType: 2) - Try to join any experience on the platform
- If other players are already in the server:
- You’ll load in, but your character will be client-only
- Other players won’t see you, and server-side events won’t fire
- If no one’s in the server:
- You’ll be placed into what looks like a self-reserved test instance
- These instances act like internal dev/test servers and don’t behave like normal live games
Launcher Logs
These logs show the launcher initially picking up the production channel, but then attempting to fetch deployment info for the zufctesting-flags-on channel — which fails with a 401 Unauthorized, causing a fallback:
2025-05-25T21:51:46Z [Bootstrapper::GetLatestVersionInfo] Got channel as production
2025-05-25T21:51:46Z [Deployment::GetInfo] Getting deploy info for channel zufctesting-flags-on
2025-05-25T21:51:46Z [HttpClientLoggingHandler::ProcessRequest] GET https://clientsettingscdn.roblox.com/v2/client-version/WindowsPlayer/channel/zufctesting-flags-on
2025-05-25T21:51:46Z [HttpClientLoggingHandler::ProcessResponse] 401 Unauthorized https://clientsettingscdn.roblox.com/v2/client-version/WindowsPlayer/channel/zufctesting-flags-on
2025-05-25T21:51:46Z [Bootstrapper::GetLatestVersionInfo] Resetting channel from zufctesting-flags-on because Unauthorized
This seems to confirm the client is trying to access an internal-only channel that my account was somehow assigned to, even though it’s not accessible to the general public.
Let me know if you’d like a suggestion for a concluding sentence or call to action.
Expected behavior
Accounts like mine should be on the standard public release channel, not placed into internal test environments like zufctesting-flags-on.
If everything were working as expected:
- Players should be able to join public servers normally, alongside others—not get pushed into solo or reserved sessions
- Gameplay should sync properly, with full client-server communication
- Accounts shouldn’t be added to internal Roblox channels unless the user has explicitly opted in or given permission
A private message is associated with this bug report
