Skip to main content
Keep your organization funded while you need its VMs or stored data. There is no guaranteed grace period at zero credit. Auto-recharge can help maintain the balance, but card failures and payment caps can interrupt it.

​
Low balance and auto-recharge

When auto-recharge is enabled and your balance falls below the configured threshold, Suji attempts to charge the default saved card. Check Settings → Payment methods for recharge settings and recent attempt information. If recharge fails or its monthly cap blocks the payment while credit remains, Suji can suspend VMs: the VM is powered off but remains allocated. Suspended and stopped VMs remain billable. The remaining balance is not a fixed recovery window; usage and other charges can change it. Add credit and resolve the payment issue promptly. Check the instance state before using its start or resume action. Updating a card or topping up does not by itself guarantee that a suspended VM restarts. With auto-recharge disabled, make top-ups manually. Suji sends low-balance notifications, but the dashboard balance and resource state are the places to check before you make operational decisions.

​
Zero balance and VM termination

When zero or negative credit is processed, VMs can be terminated. The termination flow attempts to create a system-disk snapshot before deleting the VM.
The automatic snapshot can fail, and termination can proceed without it. Keep independent backups of important data. A VM snapshot does not include attached volumes and is not a guarantee of application-consistent recovery.
A successfully recorded termination snapshot has a seven-day retention deadline. Check the snapshot’s status and expiry in the dashboard. Topping up does not extend the deadline of a termination snapshot.

​
Recover a terminated environment

  1. Top up the organization and check which snapshots and volumes are still available.
  2. Before the snapshot expires, use an available, ready snapshot to restore into a compatible new VM. Follow Snapshots.
  3. Verify the restored application and data. Review IP addresses, domains, access and separately retained volumes before sending traffic to the new environment.
  4. Confirm that the restored environment has the backups and configuration you need.
Restoring creates a new environment; it does not reverse the original VM’s deletion. Recovery depends on the available backup and its contents. Once a retained snapshot is deleted, it can no longer be restored through Suji.

​
Snapshots and volumes

Zero-balance handling can place ready manual snapshots and volumes into a seven-day retention window. Volumes are separate resources; a termination snapshot is not a copy of their data. When a positive balance is processed, Suji clears zero-balance retention on manual snapshots and returns retained volumes to an available state. This happens in the background, so check the status and deadline after topping up. If an expiry remains, contact support before it passes. Termination snapshots keep their original expiry. Managed daily backups belong to their VM and are deleted with it; they are different from separately retained snapshots. Expired retained resources are removed by background cleanup. Restoring credit after deletion does not recover them. Stored resources have separate billing rules; see VM pricing.

​
If something looks wrong

Contact dashboard Support with the organization, instance or snapshot ID, the displayed status and any expiry date. Avoid repeated destructive actions while investigating. If you still have an accessible VM, export important data before making further changes.