Pause & Resume

​

Pause and resume

prime sandbox pause sbx_123
prime sandbox resume sbx_123

client.pause(sandbox_id)
client.resume(sandbox_id)

import time

client.pause(sandbox_id)
while client.get(sandbox_id).status != "PAUSED":
    time.sleep(1)

​

What happens while paused

• Billing: a paused sandbox is billed at the disk rate only. CPU and memory charges stop.
• Timeout: paused time counts toward timeout_minutes. A sandbox that reaches its timeout while paused is terminated.
• Limits: a paused sandbox doesn’t count against your active sandbox, CPU, or memory limits. A resume is checked against them like a create, so it can be refused if you’re at a limit.
• Connections: live connections don’t survive a pause. SSH sessions, running command streams, and open TCP connections to or from the sandbox are dropped, so reconnect after resuming.
• Network policy: you can replace a paused sandbox’s egress policy. It applies on resume.
• Disk: the pause saves the sandbox’s disk as a checkpoint, which appears in prime sandbox checkpoint list. Like any checkpoint, you can restore new sandboxes from it, and its storage is billed as checkpoint storage.

​

If something goes wrong

• A pause that fails leaves the sandbox RUNNING, with the reason in its error message.
• A resume that fails leaves it PAUSED with an error message, so you can retry. If it can never succeed, the sandbox moves to ERROR.
• A paused sandbox stays on the node that paused it. If that node is lost, the sandbox is terminated.

​

Limitations

• Sandboxes with volumes attached.
• GPU sandboxes.