"Lost connection to Team Create. Please reconnect. (Error Code: 270)" is a Roblox Studio error on Windows. It appears when the place you have open falls out of sync with its Team Create session, or when Studio's connection to that session drops. Players never see this one: when a game server connection dies mid-play, it shows up as error code 277 instead.
First, the worry that actually matters: your work is almost certainly safe. In Team Create, the place saves to the cloud roughly every 4 minutes, script edits auto-save about every 5, and script drafts are stored on your own machine between Studio sessions. A disconnect usually costs a few minutes of changes at most.
| # | Fix | What it does |
|---|---|---|
| 1 | Take the reconnect prompt | Rejoins the session without closing anything |
| 2 | Close and reopen the place | Forces a fresh sync with the cloud copy |
| 3 | Restart Studio fully | Clears a session that will not resync |
| 4 | Check drafts, then save | Confirms nothing was lost |
| 5 | Test another network | Rules out your router or connection |
| 6 | Check Roblox status, work solo | Waits out problems on Roblox's side |
| 7 | Reinstall and clear AppData | Roblox's official last resort |
How to reconnect to Team Create
Work through these in order. Most disconnects end at step 1 or 2.
1. Take the reconnect prompt
When the 270 dialog offers to reconnect, use it. Studio tries to rejoin the same session in place, and if the drop was a short network blip, you are back in seconds.
2. Close and reopen the place
If reconnecting fails, close the place and open it again from the Creator Hub or your recent places list. A fresh join pulls the current cloud copy, and the session usually resyncs cleanly.
3. Restart Studio fully
If the reopened place still will not connect, quit Studio completely and launch it again. That clears a stuck session that a simple reopen cannot fix.
4. Check your script drafts, then save
Back in the session, confirm your latest script edits are still in your drafts, then commit them. From here, a quick Ctrl+S (Cmd+S on Mac) during long sessions keeps the loss window near zero even when auto-save is minutes away.
How to stop Team Create from disconnecting
If 270 hits once a week, ignore this section. If it hits every few minutes, something between your PC and Roblox is unstable, and it is worth finding out which side.
5. Test your connection on another network
Restart your router, then open the same place while tethered to a phone hotspot. If Team Create holds steady on the hotspot, the problem is your home network. A failing router can break Team Create specifically while browsing and video calls still work fine, so do not rule it out just because everything else seems healthy.
6. Check Roblox status and work solo if needed
Look at status.roblox.com for Studio or Team Create incidents. During a rough patch on Roblox's side, you can keep working alone: open the Live Collaborators window, press the ... button, and choose Disable Team Create. Turn it back on once things settle.
One more habit worth trying if you use the debugger: avoid leaving Studio paused on a breakpoint for long stretches. Some developers have seen sessions time out that way.
7. Reinstall Studio and clear the AppData folder
Roblox's official last resort for repeat 270s is a clean reinstall. Commit or copy any unsaved script drafts first, since this wipes Studio's local files.
- Uninstall Roblox Studio.
- Open File Explorer and go to the AppData\Local folder (type %LocalAppData% in the address bar).
- Delete the Roblox folder.
- Reinstall Studio from create.roblox.com and sign in again.
A clean install on a stable connection removes every local cause. If 270 still fires constantly after that, report it on the Roblox Developer Forum with details, because what remains is likely on Roblox's side.
If your Studio trouble looks more like hard crashes than dropped sessions, the fixes for Roblox closing on its own and the "unexpected error" quit popup cover that ground. The full rundown of codes lives in Roblox errors and fixes.
