You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/sandbox.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: "Sandbox lifecycle"
3
3
sidebarTitle: Lifecycle
4
4
---
5
5
6
-
Sandboxes stay running as long as you need them. By default, a sandbox will automatically pause after a period of inactivity to save resources — you can resume it at any time from the same state. You can also configure an explicit timeout or shut down a sandbox manually.
6
+
Sandboxes stay running as long as you need them. When their timeout expires, they automatically pause to save resources — preserving their full state so you can resume at any time. You can also configure an explicit timeout or shut down a sandbox manually.
7
7
8
8
<Info>
9
9
Sandboxes can run continuously for up to 24 hours (Pro) or 1 hour (Base). For longer workloads, use [pause and resume](/docs/sandbox/persistence) — pausing resets the runtime window, and your sandbox's full state is preserved indefinitely.
0 commit comments