Studio silently discards edits after a sleep-triggered Team Create disconnect, with local Auto-Recovery disabled

Bug Reports Studio Bugs
,
1

After a Team Create session is dropped due to machine sleep (Exceeded TimeAsleepDisconnectThreshold), Studio does not reconnect and does not restore local Auto-Recovery. It continues to accept edits normally for an unlimited period with no blocking indication that changes are not replicating. When a reconnect is eventually triggered — in my case by exiting a playtest — Studio rejoins and loads the last saved place version over the top of the in-memory DataModel, discarding all local edits without warning or prompt.

I lost approximately two hours of work this way. There was no crash, no error dialog, and no recovery file was written.

Impact

Three save mechanisms all fail to cover this state:

  1. Local Auto-Recovery is disabled because the place is a Team Create place (per documentation, Studio Settings Auto-Recovery applies only when collaboration is disabled).
  2. Server-side saving cannot occur because the client is not connected.
  3. The reconnect resolves the conflict server-wins, silently, with no prompt and no pre-reconnect recovery dump.

The result is an unbounded window in which a user can do real work that is guaranteed to be destroyed, with no visible signal beyond the Team Create connection indicator.

Steps to reproduce

  1. Open a place with Team Create enabled.
  2. Allow the machine to sleep long enough to exceed the Team Create sleep disconnect threshold (log reason: Exceeded TimeAsleepDisconnectThreshold).
  3. Wake the machine. Studio remains open and does not reconnect.
  4. Continue editing. Edits apply normally, undo history works, playtests run.
  5. Start and stop a playtest.
  6. On exiting the playtest, Studio reconnects to Team Create and loads the last saved place version. All edits from step 4 are lost.

Actual behaviour

Studio remains in a disconnected Team Create session indefinitely, accepts edits, then discards them on reconnect with no prompt and no recovery file.

Log evidence

Studio 0.734.0.7340915. Timestamps UTC.

Disconnect due to sleep, followed by the last Auto-Recovery written in the entire session:

2026-08-17T11:00:48.363Z [FLog::Output] TeamCreateDisconnectInfo::setReason: Exceeded TimeAsleepDisconnectThreshold
2026-08-17T11:00:49.082Z [FLog::TeamCreateManager] Disconnected due to Lost connection to the game server, please reconnect (277). LostConnection = true
2026-08-17T11:00:49.253Z [FLog::CreatorOutput] Auto Recovery successful. Place saved to '.../AutoSaves/<placeid>_AutoRecovery_8.rbxl'

Note the one-second gap — this Auto-Recovery is triggered by the disconnect event, not by the interval timer. Only two such writes occur across the 25.5-hour session, both immediately following a LostConnection = true event.

No reconnect occurs for the next 15 hours. IsReconnect: true appears only twice in the full session log: 2026-08-17T03:36:08Z and 2026-08-18T02:14:04Z. Every connection in between is a local playtest server, not Team Create:

2026-08-17T21:08:33.382Z [FLog::Output] ! Joining game '00000000-0000-0000-0000-000000000000' place <placeid> at localhost
2026-08-17T21:08:33.398Z [DFLog::NetworkClient] RbxTransport Client will connect to server 127.0.0.1|56848, udmux |0

The Auto-Recovery interval never fires during the Team Create session. Zero FLog::AutoSaveDelayOnUserInputLog entries across 25.5 hours, despite a configured 300-second interval. For contrast, a non-Team-Create session started minutes later on the same machine with identical settings fires the timer immediately:

2026-08-18T02:34:18.744Z [FLog::AutoSaveDelayOnUserInputLog] No user input within the last 5000 ms. Allowing auto-save through.
2026-08-18T02:34:18.744Z [FLog::AutoSaveDelayOnUserInputLog] Time since last auto-save attempt of 30 seconds is < user's set auto-save interval of 300 seconds. Not starting auto-save attempt.

That session logs IsTeamCreate: false; the affected session logs IsTeamCreate: true.

Playtest exit triggers the reconnect and the overwrite:

2026-08-18T02:12:30.562Z [FLog::PlaySoloManager] initiatePlaySolo: PlaceStateTransitionStatus becomes StartingPlayTest
2026-08-18T02:13:30.757Z [DFLog::RbxTransportDummyServer] Server stopped with reason: RCC: 288 (DisconnectServerShutdown)
2026-08-18T02:14:04.757Z [telemetryLog] IsReconnect: true
2026-08-18T02:14:08.710Z [FLog::TeamCreateJoinPayload] Joining game 7154795a-eeb2-499c-ba36-eaec65b7d2b6 place <placeid>
2026-08-18T02:14:09.406Z [FLog::CloseDataModel] Setting place version 265

Place version 265 was saved at 2026-08-17T10:54Z. All edits made between 2026-08-18T00:15Z and 2026-08-18T02:14Z were discarded at 02:14:09.

The affected place is private; place ID, universe ID and the disconnect incident ID are in the staff-only field.

Separate but related issue

Opening a local .rbxl from Explorer while a Team Create session is live causes RobloxStudioInstaller to terminate the running Studio processes in order to relaunch:

[FLog::DesktopInstaller] Looking for open processes matching the filename RobloxStudioBeta.exe
[FLog::DesktopInstaller] Found 2 processes matching the filename RobloxStudioBeta.exe
[FLog::UpdateManager] requestShutdown with updateState '3'

This is what initially appeared to be a crash. It occurred 19 minutes after the actual data loss so it is not the cause here, but terminating live Studio sessions to service a file-open request seems worth flagging.

System information

  • Studio version: 0.734.0.7340915
  • Git hash: daba48af7acd532126e9d1c4b3c2395182ed0748
  • OS: Windows 148.10.0.26200
  • CPU: 14 cores
  • RAM: 64 GB
  • GPU: NVIDIA GeForce RTX 4060 Laptop GPU (driver nvldumdx.dll 32.0.16.1088), D3D11
  • Team Create: enabled
  • Auto-Recovery: enabled, 5-minute interval

Beta features enabled

AssetQualityValidation, CreateAnimationFromVideo, CreateAssetAsync, CustomVideoUpload, DebuggerLuauAPI, FacialAnimationRecording, GltfExport, MVAlphaMode, NewCameraControls, NextGenDraggers, PartyEmulator, PlaytestSubagent, RemoteBreakpoints, RevampedAssetManagerRelease, SceneAnalysis, ScriptSyncM2_5, SegmentByParts, SolidModelingOnMeshes, TextureGenerator2, VideoApi

I have not tested whether disabling these changes the behaviour.

Expected behavior

When a Team Create session is disconnected, Studio should protect in-memory work by any one of the following:

  1. Re-enable local Auto-Recovery for the duration of the disconnect. While the server cannot receive changes, the local interval timer should resume so edits are captured to AutoSaves as they would be in a non-collaborative place.
  2. Write an Auto-Recovery file immediately before a reconnect replaces the DataModel. A recovery dump already fires on LostConnection = true, so the mechanism exists — it should also fire at the point the local DataModel is about to be overwritten.
  3. Prompt on reconnect when the local DataModel has unsaved changes, offering to save to file, publish the local state, or discard, rather than defaulting to server-wins silently.
  4. Surface the disconnected state unmissably — a persistent banner, or a modal on the first edit after disconnect — so the user knows their changes are not being saved before hours accumulate.

Additionally, Studio should attempt to reconnect automatically after a sleep-triggered disconnect, or at minimum on the next user interaction, rather than remaining disconnected indefinitely until an unrelated event (playtest exit) happens to trigger a rejoin.

A private message is associated with this bug report