Players unable to join game: "This experience cannot be visited at this time"

Multiple community members and staff are reporting that they are unable to join the game Georgia State Roleplay. Upon attempting to join, users are blocked by a system screen stating: “This experience cannot be visited at this time.”

Steps to Reproduce:

Expected Behavior:

  • The game should launch normally for all users.

Actual Behavior:

  • The experience is inaccessible to players, displaying the error message shown in the attached image.

Additional Information:

  • Game Settings: The game is set to Public and is configured for All Ages in the Creator Dashboard.

  • Impact: This is affecting a wide range of users, including group staff.

  • Visual Aids: Please see the attached screenshot for the specific error encountered.

3 Likes

Hi there, do you see any messaging on Creator Hub?
Or if you’re the owner, the Violations & Appeals portal or your Messages inbox?

1 Like

Hey, I am responding on the Project Owners behalf. He has no messaging on creator hub, nor anything in Violations & Appeals portal or Messages inbox.

1 Like

Hey, just want to follow you up. Roblox Appeals, even though we filed a technical bug/support, have said that the game is supposed to be fully playable and that it’s not moderated in anyway. We would appreciate a follow up on this or a look into it, due to how the game is being affected.

2 Likes

Hey, still waiting. Everything is good on our end, still dont know why its down for players, please get this fixed asap.

1 Like

It looks like the game is set to private. Can you make it public and see if players can see it?

1 Like

Everything seems to be working fine now. Players are joining and nothing is being reported.

Hey, following the backend bug that mistakenly forced our experience unplayable for an extended period, our telemetry has completely flatlined and our discovery metrics are entirely broken (showing 0.00% retention and dead active users due to the artificial blackout). Because this was a platform-side routing failure rather than game performance, could an engineer manually review or re-index our experience’s discovery weight so we aren’t permanently penalized by this bug?