Error 264 – Reconnection Fails After Disconnecting

Bug Reports Other Bugs
, , ,
#1

As of 5/5/25, this error is still occurring for me and many other players, based on my experience with friends and various videos discussing the same issue.

The problem usually appears after leaving or getting disconnected from a game. When attempting to rejoin, players often encounter Error 264:

  • “You are already playing a game. Please shut down the other game and try again.”

image

I can confirm that I have no other active logins on my account, and no one else has access to it. The error seems to happen at random, and I haven’t been able to pinpoint a consistent cause.

Typically, it takes two attempts to successfully rejoin the game before the error disappears, which is strange on its own.
I suspect it may involve some kind of forced session closure, but I can’t explain why it happens. One common theory I’ve seen in multiple discussions is that it’s related to mass requests—usually when a player tries to reconnect too quickly after disconnecting.

That said, I always wait a bit before rejoining to avoid triggering too many requests, yet the issue still persists.

Expected behavior

Most people expect to be able to rejoin a game right away after getting disconnected. Whether it’s due to a crash, a freeze, or a kick, it’s normal to think that pressing the play button again should let you back in without any problems.

But with Error 264, that doesn’t happen. Instead, we’re told we’re “already playing a game,” even though we’re not. It’s frustrating because it feels random and doesn’t make sense—especially when you know there’s no other session running.

if I get disconnected, I should be able to rejoin without having to close and reopen Roblox two or more times just to get past this error. It really interrupts the experience and makes reconnecting way more annoying than it should be.

2 Likes
#2

This has also occured to me. To fix it I usually wait a minute, then quit Roblox and reopen it. That’s how I do it, it might not work for everyone.

1 Like
#3

It does work.
The thing is, I’m trying to figure out what’s causing the issue and find a fair solution that doesn’t take too much time.
It’s actually a common problem for a lot of players among the platform.

2 Likes
#4

FWIW on some freezes/crashes, Roblox doesn’t properly close and still has a process or two hanging around in the background. This can cause Roblox to think that you’re still playing.

I’d imagine it’s a similar situation here, just more on Roblox’s end - Your client disconnects for some unexpected reason, but Roblox isn’t able to process it in time (maybe it hasn’t timed out, maybe it didn’t get the “player has left” packet right) so it still thinks you’re playing the game until it finally registers that you aren’t actually in anything.

2 Likes
#5

This explanation is helpful, thank you for clarifying things.
However, this issue should be addressed, as it causes significant problems for many players in the platform.

the fix involves waiting, which in my opinion, shouldn’t be necessary in the first place considering this issue has been around for quite a while now.

#6

Your client disconnects for some unexpected reason, but Roblox isn’t able to process it in time (maybe it hasn’t timed out, maybe it didn’t get the “player has left” packet right) so it still thinks you’re playing the game until it finally registers that you aren’t actually in anything.

This is a good description of the problem. Sometimes our server doesn’t get the notification from your client that it’s closing the connection, so the server has to wait for your connection to timeout before it removes you. If you try to join the same server again during the timeout period, you see the 264 error code.

We’re currently working on improving the detection of this situation and allowing you to rejoin without having to wait for the full timeout. There are some limitations that won’t let us totally remove the 264 error code, but our goal is to significantly reduce it.

1 Like