I am unable to join the Team Create session for my place. Roblox Studio shows a timeout error when trying to connect to the Team Create server. The error reads:
“We could not join the Team Create session for place [14055194604]. Timeout on connect, unable to initialize Team Create server: code 0”
This happens every time I try to join Team Create for this specific place.
Recent findings, trying to open a rbxl of the affected game returns a different error. Our team found that reverting the place back to an older version makes it able to be opened via an rbxl. The affected place did start working shortly afterwards.
We also had a second place affected, that was only broken for one team member consistently. Again, sending an rbxl did not work but downloading a previous version opened with no issues
Yeah, this issue is spreading to multiple of our places, even some under different groups. I think there is an issue with my account as I am enrolled in a beta program. I think that might be interferring with the places I work in as the issue is following me and the places I enter, even if I make no changes.
Hello, I’ve been digging into this and checking through our logs today and I haven’t been able to find any problems that happened recently. Looking over the last three days I see this place being started as a Team Create server several times and each of those times no one joined and the server shut down after a minute, which is what we expect to happen.
If you can, would you mind giving joining another try so I can get some fresh logs to look at? Also please post a fresh screenshot of the failure message when you do. Can look into this deeper as soon as I hear back from you.
Hello, quick question regarding this. Do you ever create your place files with something like Rojo and then upload to roblox through Open Cloud, or do you do all of your editing through studio? I ask becasue rojo is known to be able to generate bad files if you configure it incorrectly, but Studio should be writing out valid files 100% of the time.
If it is Studio that saved out the bad file I can escalate this internally because that would be a very serious problem.
We do not use Rojo or upload places through the Open Cloud, we just use a Team Create place and do it directly in Studio.
I believe this is an issue related to those in the beta channel or maybe some undocumented A/B testing going on as it seems to be only Chloe’s account breaks it in other places she joins.
There’s also seemingly two issues not just one and I believe they might be both related to beta features:
Place corruption can cause the Team Create error as posted by the OP, but if we download that version of the place we get a more explicit error message (via assetdelivery):
The other problem is Chloe occasionally has to rejoin because other devs become unable to join due to our Studio clients supposedly going out of date (even though it was in the same day), but this is more an inconvenience.
Hello, no we do not use Rojo. @Jakedies is one of our team members working on the same game, so all information he has provided to this thread is related directly to my issue and he has explained it better than I could!! Thanks so much for looking into this
Right now it looks like the most likely cause is that somehow the new beta CSG system was used when saving that file, though it is still unclear exactly how that happened.
This new system is currently an opt-in beta that was only offered to a limited number of users and after talking with some people internally it looks like none of the people reporting problems in this thread were on the beta. We’re still figuring out exactly what might have happened here.
We’re looking into what we can do to fix up a place file broken like this but in the meantime you may be able to roll back to a good version on your own but the process is a little tedious.
Then, make a new shortcut to RobloxStudio with the extra command line flags -task EditPlaceRevision -placeId PLACE_ID_HERE -universeId UNIVERSE_ID_HERE -placeVersion VERSION_HERE
From that unfortunately you’ll just have to walk backwards through your versions until you find one that works, then you can re-upload that one and continue working in Team Create.
If you check this out and rolling back like that would cause you to lose significant progress let me know and I can see if we can instead fix up the bad data in the latest version of the place.
@chloeb3000 as well because I can only directly reply to one person.
I am a member of the Roblox Research Panel and did have access to the beta features, however I don’t believe I had them enabled, but I could be wrong. This issue started for me when the new build was pushed to us on Friday. This explanation makes sense for my case, but not for the original poster of this bug who posted this way before it was an issue for us.
Thank you for the guidance on the best way forward with this. I think majority of our places should be good to work in now, thank you
Right now it looks like the most likely cause is that somehow the new beta CSG system was used when saving that file, though it is still unclear exactly how that happened.
Yes, I think this is the cause based on the error message that I was getting when I try opening up one of the older but still recent versions.
I have an update for you as well for place 14055194604.
After some recent joins I was able to find a few good server logs and it looks like the problem is that the latest version of your place is right at the memory limit of the server which is making it so the server can’t start up.
I recommend following my instructions above to roll back to an older version which uses less memory.
Then, make a new shortcut to RobloxStudio with the extra command line flags -task EditPlaceRevision -placeId PLACE_ID_HERE -universeId UNIVERSE_ID_HERE -placeVersion VERSION_HERE
On our end I’ll continue looking into how this could have happened, because if a place takes up too much memory it should not be possible to save it in the first place, but somehow that has happened in this case.
We managed to restore an earlier version, but when we start adding the things we have developed so far, it suddenly crashes and there is no way back to the place. Currently (on September 27), we are working carefully with 5-minute backups, and if it crashes, we restore it, but we don’t want to do this in the long run.
