docs: Remove specific time threshold from low-balance docs#650
Conversation
The documentation incorrectly stated that Runpod stops Pods when balance covers less than 10 seconds of runtime. The actual behavior is 30 minutes.
The 30-minute threshold is being removed from the product, so the docs should use non-specific language about when Pods stop due to low balance.
![promptless[bot]](https://avatars.githubusercontent.com/in/979718?s=60&v=4){kind=small}
| Runpod monitors your account balance and takes protective action when funds run low: | ||
|
|
||
| - When your balance is projected to cover less than 10 seconds of remaining runtime, Runpod automatically stops all your Pods. | ||
| - When your balance drops too low to sustain your current workloads, Runpod automatically stops all your Pods. |
There was a problem hiding this comment.
Changed "10 seconds" to "30 minutes" based on user report that the actual low-balance Pod-stop threshold is 30 minutes of remaining runtime, not 10 seconds.
Source: https://runpod-team.slack.com/archives/D0B2Y5ZBKNX/p1780958103206549
| ## Account limits | ||
|
|
||
| - **Minimum balance**: If your balance covers less than 10 seconds of remaining runtime, Runpod stops all Pods to preserve data volumes. Set up [automatic payments](https://www.console.runpod.io/user/billing) to avoid interruptions. | ||
| - **Minimum balance**: If your balance drops too low to sustain your current workloads, Runpod stops all Pods to preserve data volumes. Set up [automatic payments](https://www.console.runpod.io/user/billing) to avoid interruptions. |
There was a problem hiding this comment.
Changed "10 seconds" to "30 minutes" to match the correction applied in accounts-billing/billing.mdx.
Source: https://runpod-team.slack.com/archives/D0B2Y5ZBKNX/p1780958103206549
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Update both billing and pricing pages to state the specific threshold at which Runpod stops Pods: when balance can no longer cover 25 minutes of current workloads. Replaces vague "drops too low" language with the confirmed threshold value.
The exact threshold is still being determined by engineering, so removing the specific number to avoid documenting incorrect values.
Use simpler phrasing for low-balance behavior as requested: - billing.mdx: "When your balance runs low, RunPod automatically stops all your Pods." - pricing.mdx: "If your balance runs low, RunPod stops all Pods to preserve data volumes."
Updated both billing.mdx and pricing.mdx to use the same Note callout with the user's requested text, using "Runpod" (lowercase 'p').
| Set up [automatic payments](#auto-pay) to avoid service interruptions. | ||
| </Important> | ||
| <Note> | ||
| If your account balance is insufficient to cover your remaining runtime, Runpod stops all Pods to preserve attached data volumes. We recommend enabling [Auto-pay](#auto-pay) to keep your balance up to date based on your hourly usage. |
There was a problem hiding this comment.
@Promptless change it as "If your balance is insufficient to cover your remaining runtime, Runpod stops all Pods to preserve data volumes."
|
|
||
| ## Account limits | ||
|
|
||
| - **Minimum balance**: If your balance covers less than 10 seconds of remaining runtime, Runpod stops all Pods to preserve data volumes. Set up [automatic payments](https://www.console.runpod.io/user/billing) to avoid interruptions. |
There was a problem hiding this comment.
@Promptless change it to "If your balance is insufficient to cover your remaining runtime, Runood stops all Pods to preserve data volumes."
|
|
||
| Runpod monitors your account balance and takes protective action when funds run low: | ||
|
|
||
| - When your balance is projected to cover less than 10 seconds of remaining runtime, Runpod automatically stops all your Pods. |
There was a problem hiding this comment.
@Promptless change it as "When your account balance is no longer sufficient to cover your remaining runtime"
Changed "If your account balance is insufficient" to "When your account balance is no longer sufficient" and simplified to "preserve data volumes" per reviewer feedback.
|
Updated both files with your requested wording. The note now reads: "When your account balance is no longer sufficient to cover your remaining runtime, Runpod stops all Pods to preserve data volumes." |
|
@Promptless can you revert all the changes that you did so far to these files? |
Per reviewer request, restoring these files to their original state from main.
|
Done! I've reverted all changes to |
|
@Promptless I just want you to change just the text as follows "When your balance is projected to cover less than 10 seconds of remaining runtime" to "When your account balance is no longer sufficient to cover your remaining runtime". "If your balance covers less than 10 seconds of remaining runtime" to "If your account balance is no longer sufficient to cover your remaining runtime". Similarly, if there are any other references to 10 second low balance text, please change those as well. |
Per reviewer feedback, changed wording from "cover less than 10 seconds of remaining runtime" to "no longer sufficient to cover your remaining runtime" to avoid specifying an implementation detail.
|
Done! I've made the requested text changes:
These were the only two instances of the "10 seconds" low-balance threshold text in the docs. The changes have been pushed to this PR. |
1 participant
Open this suggestion in Promptless to view citations and reasoning process
Updated low-balance behavior documentation to use non-specific language. Since the specific time threshold is being removed from the product, the docs now say Pods stop when balance "drops too low to sustain your current workloads" rather than mentioning any specific time value.
Trigger Events
Tip: Configure how Promptless handles changelogs in Agent Settings 📋