Skip to main content
Sandbox snapshot retention has no scheduled auto-delete by default, but storage must remain funded. You can set an explicit expiry, change it, or clear it.

​
Read retention state

Inspect retainUntilMs, storedBytes, monthlyStorageUsd, graceState, graceDeadlineMs, and warnings. A null retainUntilMs means there is no scheduled expiry.

​
Set an expiry

The create API accepts retentionSeconds with a minimum of 60 seconds and no 24-hour maximum:
To change an existing snapshot’s retention, save this as retention.json:
Read the resulting deadline from snapshot detail. Save {} as retention.json and submit it to the same endpoint to clear scheduled expiry; null is also accepted for retentionSeconds.

​
Keep storage funded

Retained snapshot storage is metered by unique retained bytes and funded through prepaid credit. Run bead pricing or call GET /v1/pricing for current rates. Storage funding uses credit grace and deadline warnings. Add credit before the reported grace deadline. Clearing an optional expiry does not remove the funding requirement.

​
Retire a snapshot

Retirement prevents new creates from that snapshot. Existing machines retain their own references. Do not use retirement as a way to change the contents of an immutable version; capture a new snapshot instead. See snapshot creation and persistent volumes for their separate retention rules.