Skip to content

Commit d74c33b

Browse files
committed
Align lifecycle page with timeout-expiry framing
1 parent 450ab0c commit d74c33b

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/sandbox.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: "Sandbox lifecycle"
33
sidebarTitle: Lifecycle
44
---
55

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.
77

88
<Info>
99
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

Comments
 (0)