From bb444c567ac6ea610633585d665e2085c50184ce Mon Sep 17 00:00:00 2001 From: lgunreddi Date: Tue, 21 Jul 2026 19:34:21 -0400 Subject: [PATCH 1/8] Update manage-pods.mdx --- pods/manage-pods.mdx | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/pods/manage-pods.mdx b/pods/manage-pods.mdx index 626ade90..4adcfd51 100644 --- a/pods/manage-pods.mdx +++ b/pods/manage-pods.mdx @@ -240,6 +240,31 @@ curl --request DELETE \ +--- +ADD TO: pods/manage-pods.mdx +PLACEMENT: New section after "Terminate a Pod", before "View logs" +--- + +## Lock a Pod + +Locking a Pod prevents accidental termination through the console UI. When a Pod is locked, the **Terminate** button is disabled and you must unlock the Pod before you can delete it. + +To lock or unlock a Pod: + +1. Open the [Pods page](https://www.console.runpod.io/pods) and expand your Pod. +2. Click the three-dot menu and select **Lock Pod** or **Unlock Pod**. + + +**Pod locking does not protect against deletion due to insufficient account balance.** If your account balance reaches $0 and is not replenished, a running Pod will be permanently deleted within approximately 2 hours — regardless of whether it is locked. + +To protect production workloads from this, enable [auto-pay](/accounts-billing/billing#auto-pay). + + +| Locking protects against | Locking does NOT protect against | +|--------------------------|----------------------------------| +| Accidentally clicking Terminate in the console | Deletion due to $0 account balance | +| Unintentional Pod deletion by team members | Runpod stopping Pods when funds are low | + ## View logs Pods provide two log types: From 24b05d553fa6a5836fd38c9dd4619ca7f04a9ce4 Mon Sep 17 00:00:00 2001 From: lgunreddi Date: Tue, 21 Jul 2026 19:39:50 -0400 Subject: [PATCH 2/8] Update billing.mdx --- accounts-billing/billing.mdx | 35 ++++++++++++++++++++--------------- 1 file changed, 20 insertions(+), 15 deletions(-) diff --git a/accounts-billing/billing.mdx b/accounts-billing/billing.mdx index 50270c4a..2f8425e8 100644 --- a/accounts-billing/billing.mdx +++ b/accounts-billing/billing.mdx @@ -20,18 +20,17 @@ You can view your current balance and recent transactions on the Billing page at ### Low balance behavior -Runpod monitors your account balance in real time. Billing runs every 5 minutes, and charges are deducted continuously based on the resources you have running. - -When your balance reaches \$0, Runpod automatically stops all of your running Pods. What happens to your data depends on whether the Pod has a network volume attached: - -- Pods with a network volume attached are stopped, and your data is preserved on the network volume. -- Pods without a network volume are terminated, and their data can't be recovered. - -Storage charges continue to accrue on network volumes while your Pods are stopped. If your balance stays at \$0 and these charges can't be covered, the network volume may eventually be terminated, and its data can't be recovered. - - -To avoid unexpected interruptions, enable [low balance notifications](#low-balance-notifications) or set up [auto-pay](#auto-pay). - +Runpod monitors your account balance and takes protective action when funds run low: + +- When your account balance is no longer sufficient to cover your remaining runtime, Runpod automatically stops all your running Pods. +- Stopped Pods retain their volume storage, but you continue to accrue storage charges. +- If your balance reaches $0 and is not replenished, **running Pods are permanently deleted within approximately 2 hours**. Stopped Pods are not immediately deleted but may be removed if the balance remains at $0. + +Deleted Pods and their data cannot be recovered. [Network volumes](/storage/network-volumes) are billed and managed separately and are not deleted on the same timeline as Pods. + + +**For production workloads, enable [auto-pay](#auto-pay).** Auto-pay reloads your balance automatically before it reaches $0, preventing Pod deletion. Manual top-ups may not be fast enough to avoid deletion once the process has started. + ### Low balance notifications @@ -48,16 +47,22 @@ Runpod sends an email when your balance falls below the threshold you set. This ### Auto-pay Auto-pay automatically reloads your account balance when it falls below a threshold, helping you avoid service interruptions from low funds. - + + +If you are running production workloads, enable auto-pay. A running Pod can be permanently deleted within approximately 2 hours of your balance reaching $0. Manual top-ups may not be fast enough to prevent deletion. + To configure auto-pay: - + 1. Navigate to the [Billing page](https://www.console.runpod.io/user/billing) in the Runpod console. 2. Add a credit card to your account if you haven't already. 3. Enable auto-pay and configure your settings: - **Threshold**: The balance at which auto-pay triggers. - **Amount**: The dollar amount to add when triggered. - When your balance drops near your configured threshold, Runpod charges your default saved card for the auto-pay amount. To prevent excessive charges, auto-pay attempts are limited to once per hour. + + +Set your low balance threshold high enough to cover several hours of your expected spend, not just a few minutes. If your threshold is too low, your balance may reach $0 before auto-pay can trigger. + ### Minimum balance requirements From 51afac9ec31a4f768042c555de5a43002f0228b9 Mon Sep 17 00:00:00 2001 From: lgunreddi Date: Tue, 21 Jul 2026 19:44:46 -0400 Subject: [PATCH 3/8] Update manage-pods.mdx --- pods/manage-pods.mdx | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/pods/manage-pods.mdx b/pods/manage-pods.mdx index 4adcfd51..facced5e 100644 --- a/pods/manage-pods.mdx +++ b/pods/manage-pods.mdx @@ -240,11 +240,6 @@ curl --request DELETE \ ---- -ADD TO: pods/manage-pods.mdx -PLACEMENT: New section after "Terminate a Pod", before "View logs" ---- - ## Lock a Pod Locking a Pod prevents accidental termination through the console UI. When a Pod is locked, the **Terminate** button is disabled and you must unlock the Pod before you can delete it. @@ -254,11 +249,10 @@ To lock or unlock a Pod: 1. Open the [Pods page](https://www.console.runpod.io/pods) and expand your Pod. 2. Click the three-dot menu and select **Lock Pod** or **Unlock Pod**. - -**Pod locking does not protect against deletion due to insufficient account balance.** If your account balance reaches $0 and is not replenished, a running Pod will be permanently deleted within approximately 2 hours — regardless of whether it is locked. + +Pod locking does not protect against deletion due to insufficient account balance.** If your account balance reaches $0 and is not replenished, a running Pod will be permanently deleted within approximately 2 hours, regardless of whether it is locked. To protect production workloads from this, enable [auto-pay](/accounts-billing/billing#auto-pay). - | Locking protects against | Locking does NOT protect against | |--------------------------|----------------------------------| From 18cca9bc5ad6b9b49e86149e4ee6ca0914e9d07e Mon Sep 17 00:00:00 2001 From: lgunreddi Date: Tue, 21 Jul 2026 19:46:23 -0400 Subject: [PATCH 4/8] Update billing.mdx --- accounts-billing/billing.mdx | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/accounts-billing/billing.mdx b/accounts-billing/billing.mdx index 2f8425e8..39a62e73 100644 --- a/accounts-billing/billing.mdx +++ b/accounts-billing/billing.mdx @@ -24,12 +24,10 @@ Runpod monitors your account balance and takes protective action when funds run - When your account balance is no longer sufficient to cover your remaining runtime, Runpod automatically stops all your running Pods. - Stopped Pods retain their volume storage, but you continue to accrue storage charges. -- If your balance reaches $0 and is not replenished, **running Pods are permanently deleted within approximately 2 hours**. Stopped Pods are not immediately deleted but may be removed if the balance remains at $0. +- If your balance reaches $0 and is not replenished, running Pods are permanently deleted within approximately 2 hours. Stopped Pods are not immediately deleted but may be removed if the balance remains at $0. Deleted Pods and their data cannot be recovered. [Network volumes](/storage/network-volumes) are billed and managed separately and are not deleted on the same timeline as Pods. - - -**For production workloads, enable [auto-pay](#auto-pay).** Auto-pay reloads your balance automatically before it reaches $0, preventing Pod deletion. Manual top-ups may not be fast enough to avoid deletion once the process has started. +For production workloads, enable [auto-pay](#auto-pay). Auto-pay reloads your balance automatically before it reaches $0, preventing Pod deletion. Manual top-ups may not be fast enough to avoid deletion once the process has started. ### Low balance notifications From 2da6cd3829fc273797f4dec8f314c3528b06eb45 Mon Sep 17 00:00:00 2001 From: lgunreddi Date: Tue, 21 Jul 2026 19:49:24 -0400 Subject: [PATCH 5/8] Update manage-pods.mdx --- pods/manage-pods.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pods/manage-pods.mdx b/pods/manage-pods.mdx index facced5e..b751b2ba 100644 --- a/pods/manage-pods.mdx +++ b/pods/manage-pods.mdx @@ -250,7 +250,7 @@ To lock or unlock a Pod: 2. Click the three-dot menu and select **Lock Pod** or **Unlock Pod**. -Pod locking does not protect against deletion due to insufficient account balance.** If your account balance reaches $0 and is not replenished, a running Pod will be permanently deleted within approximately 2 hours, regardless of whether it is locked. +Pod locking does not protect against deletion due to insufficient account balance. If your account balance reaches $0 and is not replenished, a running Pod will be permanently deleted within approximately 2 hours, regardless of whether it is locked. To protect production workloads from this, enable [auto-pay](/accounts-billing/billing#auto-pay). From b5aa98bf5f62bc00d961d79ba7901713791cec3e Mon Sep 17 00:00:00 2001 From: lgunreddi Date: Tue, 21 Jul 2026 19:53:01 -0400 Subject: [PATCH 6/8] Update billing.mdx --- accounts-billing/billing.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/accounts-billing/billing.mdx b/accounts-billing/billing.mdx index 39a62e73..e3e6ed51 100644 --- a/accounts-billing/billing.mdx +++ b/accounts-billing/billing.mdx @@ -25,6 +25,7 @@ Runpod monitors your account balance and takes protective action when funds run - When your account balance is no longer sufficient to cover your remaining runtime, Runpod automatically stops all your running Pods. - Stopped Pods retain their volume storage, but you continue to accrue storage charges. - If your balance reaches $0 and is not replenished, running Pods are permanently deleted within approximately 2 hours. Stopped Pods are not immediately deleted but may be removed if the balance remains at $0. + Deleted Pods and their data cannot be recovered. [Network volumes](/storage/network-volumes) are billed and managed separately and are not deleted on the same timeline as Pods. For production workloads, enable [auto-pay](#auto-pay). Auto-pay reloads your balance automatically before it reaches $0, preventing Pod deletion. Manual top-ups may not be fast enough to avoid deletion once the process has started. From 6a213acde118c05cca1596b8bb55a6bf5734f992 Mon Sep 17 00:00:00 2001 From: lgunreddi Date: Tue, 21 Jul 2026 19:54:17 -0400 Subject: [PATCH 7/8] Update billing.mdx --- accounts-billing/billing.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/accounts-billing/billing.mdx b/accounts-billing/billing.mdx index e3e6ed51..4b376957 100644 --- a/accounts-billing/billing.mdx +++ b/accounts-billing/billing.mdx @@ -23,7 +23,7 @@ You can view your current balance and recent transactions on the Billing page at Runpod monitors your account balance and takes protective action when funds run low: - When your account balance is no longer sufficient to cover your remaining runtime, Runpod automatically stops all your running Pods. -- Stopped Pods retain their volume storage, but you continue to accrue storage charges. +- Stopped Pods retain their volume storage, but you continue to accrue storage charges. - If your balance reaches $0 and is not replenished, running Pods are permanently deleted within approximately 2 hours. Stopped Pods are not immediately deleted but may be removed if the balance remains at $0. From 1af3ed94527c006126f05135ea459911553c3e4f Mon Sep 17 00:00:00 2001 From: lgunreddi Date: Wed, 22 Jul 2026 09:27:50 -0400 Subject: [PATCH 8/8] Update billing.mdx --- accounts-billing/billing.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/accounts-billing/billing.mdx b/accounts-billing/billing.mdx index 4b376957..1cb0c5e0 100644 --- a/accounts-billing/billing.mdx +++ b/accounts-billing/billing.mdx @@ -24,7 +24,7 @@ Runpod monitors your account balance and takes protective action when funds run - When your account balance is no longer sufficient to cover your remaining runtime, Runpod automatically stops all your running Pods. - Stopped Pods retain their volume storage, but you continue to accrue storage charges. -- If your balance reaches $0 and is not replenished, running Pods are permanently deleted within approximately 2 hours. Stopped Pods are not immediately deleted but may be removed if the balance remains at $0. +- If your balance reaches \$0 and is not replenished, running Pods are permanently deleted within approximately 2 hours. Stopped Pods are not immediately deleted but may be removed if the balance remains at \$0. Deleted Pods and their data cannot be recovered. [Network volumes](/storage/network-volumes) are billed and managed separately and are not deleted on the same timeline as Pods.