I simply cannot join ANY of my Team Create Studios

[DevForHire]

As you can see, it errors nonstop for every attempt to open a team create studio. I’m unsure of how to resolve this, but it is urgent that I join and finish the work I need to.

Last time this happened, it was an IP Address issue, but it’s different this time, switched to 3 different Wifi networks and nothing has worked.

Expected behavior

Generally I’m able to join any of my team create studios, and I simoply cannot,

A private message is associated with this bug report

[Hooksmith]

Hey, this is probably the same issue as here: When Studio updates and an offline collaborator has Team Create open, nobody can open that game

There are some mitigation steps in the thread there you can attempt. I’ll bump this issue with the right team internally. Apologies for the inconvenience.

[swagalier2000]

Hello @DevForHire thanks for the report. Could you send over a copy of the studio logs from a recent failed attempt to open? This will contain info which can help debug the issue for your place. We will investigate this now.

To find your Roblox Studio log files, you can follow these instructions based on the operating system you are using:
For Windows:

1. Open the Run dialog by pressing the WINDOWS KEY and R at the same time.
2. Type %LOCALAPPDATA%\Roblox\logs and press Enter.
3. The log files will be displayed. They typically have the format <version>_<timestamp>_Studio_XXXXX.log.

For Mac:

1. Open Finder, then select the Go menu.
2. Click on Go to Folder.
3. Type ~/Library/Logs/Roblox and press Enter. This will open the directory containing your Studio logs.

If Roblox Studio has crashed, the .dmp files can be found in a specific subdirectory:

1. For Windows, they are moved to the logs\archive folder.
2. For Mac, you can find the .dmp file directly in the tmp directory. Open Terminal and run open $TMPDIR, then look for the .dmp file.

These steps should help you locate your Roblox Studio log files for troubleshooting

[DevForHire]

I’m happy to say my issue has been resolved (For the moment.)

I seemingly had an update, and as soon as I updated, the issue has since been resolved.

I will keep this thread open in case of any issues I have in the future, hopefully this is the last issue.