Skip to main content

Broken pods

Sometimes a pod's status turns red and reads BROKEN. This means the GPU provider force-closed your pod — the container and your rental are already gone. Hover the status for the in-app note:

This pod was force-closed by the provider. You have been credited. You can delete it.

What it means for you​

  • Billing has stopped and you've been credited for the interrupted rental — you aren't charged for a broken pod.
  • The pod is a dead shell. Anything that wasn't on a Volume or in a Backup is gone.

What you can do​

A broken pod can only be deleted. Every other action is disabled, because there's no live container to act on:

  • ❌ Reboot, edit, switch template, install Jupyter, add/remove SSH keys
  • ❌ Back up or restore
  • ✅ Delete — removes the pod from Your Pods

Open the pod and click DELETE.

Renting the same node again​

To rent the same machine again, delete the broken pod first. If you try to rent it while the broken pod is still there, the rental is blocked with a message that names the pod to remove — for example:

This node still has a broken pod (<pod_id>) that must be removed before you can rent it again. Please delete the broken pod first.

Delete the broken pod, then deploy as usual from Create a pod.

For agents and automation: API
# Delete a broken pod
curl -X DELETE https://lium.io/api/pods/<pod_id> \
  -H "X-API-Key: $LIUM_API_KEY"

A pod's status is BROKEN once the provider force-closes it. Any mutating call on it (reboot, edit, switch-template, install-jupyter, SSH keys, backup, restore) returns 400 — only delete succeeds. Renting the node again while your broken pod still exists also returns 400, with the broken pod's id in the message, until you delete it. Get an API key first.