Recent increase in failed teleports (Error code 773 and 279)

[Panwellz]

Recently, I’ve been seeing an increasing amount of reports about failed teleports in Car Crushers 2

The errors usually mention the target place being restricted, but it doesn’t happen anywhere close to 100% of the time. These are some of the user reports I’ve been seeing:

In Car Crushers 2 we have an automatic refresh system that teleports players into a holding place before a server shuts down, and then it teleports them back into the place ID that they came from. The “Restricted Area” error seems to primarily happen when teleporting to this holding place. But not when teleporting between any of the game’s other places (That I know of)

The system works like this right now:

1. When game:BindToClose is invoked, the following code runs to teleport players to the holding place
   
   
2. When all players have arrived in the holding place, we run this to teleport them back. “Destination” is the place ID that the party came from:
   
   
3. If the teleport failed or if any players remain after 15s, we run this to teleport remaining players into the same place
   
   

I believe step 2 or 3 is what caused error 279 in the 2nd user report shown above. While the other error usually happens in step 1.

The same issue happened when we used “Restart old Servers” option earlier this week for an update. Several servers/players encountered this error which prevented some servers from refreshing.

[music_man1996]

Thanks for the report! Just sent this one to the team. We’ll update you as soon as we can.

[unahb4]

Hi, following up here. Is this something you are still observing at an increased rate? Thanks!

[Panwellz]

I haven’t seen any more reports of this the past 5 days. But it seems to be more common when we restart all servers at the same time, which used to be a non-issue. (Using the feature to restart servers for an update). I could let you know about the results here the next time I do this

[Panwellz]

Haven’t noticed any more issues so I’m marking this as resolved

[Sky_Fox7071]

I’v seen that same exact error whenever cc2 refreshes.

It happens to me every single time the game refreshes.

EDIT:
Then when I leave and try to rejoin it will pop that same message again so I have to wait a couple minutes until I can join back the game its super weird.

[Lucatacos2213 (Lucatacos)]

As a player, I’m still getting this error (I got this after joining a game, got a roblox update and after I got this error)
It’s very random, I don’t know how to reproduce it every time

[Abcreator]

I’ve been able to pretty consistently reproduce this every time I join a place just after starting up Roblox for the first time since a PC shutdown; re-joining the place (IE: trying the teleport again after relaunching) or leaving Roblox open for a while before playing fixes the issue.

[Panwellz]

Alright sounds like this is not sorted then. Would you be able to send me your discord username so I can try an intentional shutdown of your server?

[MythicalRealm_Studio (Studio)]

Hey i am not sure if that’s related but after the outage some of projects i worked on
has an issue with httpservice error was number of requests exceeded which didn’t happen only happened after the outage? even though we don’t reach rate limit

[Sky_Fox7071]

Of course add me → sky_fox7071

[Panwellz]

@unahb4 @PageFaults I just spoke to sky_fox about this. Apparently the issue only happens for him when the server shuts down with CloseReason being “OutOfMemory”.

I just did a few manual shutdowns with him but all of them worked flawlessly. But seemingly the issue has always happened when the server was displaying Car Crushers 2’s “OutOfMemory” information prior to the teleport.

It seems like players affected by this also can’t rejoin the game for several minutes afterwards (The same exact message will keep popping up when they join)

[PageFaults]

Hey Panwellz,

Unfortunately shutting down due to running out of memory is currently unreliable. This is mostly related to the nature of the server running out of memory. We’re attempting a shutdown, but if the server continues to try and ues more and more memory we will eventually forcefully close it.

Sometimes it’s taking up memory so quickly we need to forcefully shut it down before you’re bindToClose functions finish running or before player teleports finish.

[Panwellz]

Is it recommended to avoid teleporting players if a server runs out of memory in that case? And does the regular “Reconnect” popup still work in this case?

One of the main problems we have is that the players who fail to teleport can’t even join the game for several minutes afterwards, as if they get softlocked from the failed teleport.

[PageFaults]

If you’re running into a problem where a user can’t join due to being “soft-Locked” I would suggest avoiding teleporting them when running out of memory (OOM) until we can further investigate the issue.

[PageFaults]

@Panwellz

does the regular “Reconnect” popup still work in this case?

It should. still work the same in this case.