Update manage-pods.mdx

accounts-billing/billing.mdx

@@ -20,18 +20,16 @@ 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.
+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.
 
-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.
-
-<Important>
-To avoid unexpected interruptions, enable [low balance notifications](#low-balance-notifications) or set up [auto-pay](#auto-pay).
-</Important>
+<Warning>
+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.
+</Warning>
 
 ### Low balance notifications
 
@@ -48,16 +46,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.
-
+
+<Warning>
+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.
+</Warning>
 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.
+
+<Tip>
+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.
+</Tip>
 
 ### Minimum balance requirements
 

pods/manage-pods.mdx

@@ -240,6 +240,25 @@ curl --request DELETE \
 </Tab>
 </Tabs>
 
+## 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: