E2B icon indicating copy to clipboard operation
E2B copied to clipboard

Paused sandbox is not persisting the file changes / addition after second time resumed and onward

Open byrizki opened this issue 5 months ago • 1 comments

Describe the bug When a sandbox environment is paused and resumed multiple times, file changes or additions are not persisted after resuming. On the first resume, changes are retained as expected, but after subsequent resumes, file modifications and new files are lost.

To Reproduce Steps to reproduce the behavior:

  1. Go to the sandbox environment.
  2. Create or edit a file (e.g., add test.txt or modify existing code).
  3. Pause the sandbox.
  4. Resume the sandbox → changes persist (works correctly).
  5. Do some edit, or add file
  6. Pause the sandbox again.
  7. Resume the sandbox → file changes/additions are gone (bug occurs).

Expected behavior File changes and additions should persist after every resume, not just the first one.

Additional context

  • resuming
Sandbox.connect(currentRunningSandbox?.sandboxId || currentPausedSandbox?.sandboxId, { timeoutMs: sandboxTimeout })
  • creation
Sandbox.betaCreate(template, {
      metadata: {
        template,
        userID: userId,
        roomID: roomId,
        createdAt: new Date().toISOString(),
      },
      timeoutMs: sandboxTimeout,
      autoPause: true,
    })

byrizki avatar Aug 29 '25 22:08 byrizki

I have the same use case. Is this bug fixed already?

debajyoti-truefoundry avatar Dec 09 '25 05:12 debajyoti-truefoundry