Sandboxes

dn sandbox is the compute-inspection subcommand. Use it when you need to see or clean up the actual hosted sandboxes behind platform workflows.

What the sandbox CLI is for

Use it to:

• list running, paused, or killed sandboxes
• inspect one sandbox in detail
• fetch sandbox server logs
• see aggregate usage for the current organization
• delete a stuck or unwanted sandbox

dn sandbox list --state running
dn sandbox get <provider-sandbox-id>
dn sandbox logs <provider-sandbox-id>
dn sandbox usage --json
dn sandbox delete --yes <provider-sandbox-id>

The identifier that matters

The sandbox CLI expects the provider sandbox ID, not the internal database UUID.

Note

If dn sandbox get or dn sandbox delete returns 404 for an ID you copied from another API surface, check whether you used the internal sandbox UUID instead of provider_sandbox_id.

List sandboxes

dn sandbox list --state running
dn sandbox list --state paused --state killed
dn sandbox list --project-id 11111111-2222-3333-4444-555555555555
dn sandbox list --json

Important details:

• --state is repeatable
• --project-id uses the explicit project UUID, not the project key
• sandbox list uses the active organization but does not infer a project filter unless you pass it

Get logs and usage

dn sandbox logs <provider-sandbox-id>
dn sandbox usage
dn sandbox usage --json

Use usage when you want the compute summary for the active organization rather than one sandbox.

Delete a sandbox

dn sandbox delete <provider-sandbox-id>
dn sandbox delete --yes <provider-sandbox-id>

Without --yes, the CLI will prompt for confirmation.

When to reach for this page

If an evaluation, optimization job, training job, or runtime looks stuck, the sandbox CLI is often the fastest way to verify whether the underlying compute is still alive.