--- title: "Why Insulin Paused AI, and How to Fix Each Case" url: https://www.insulin.dev/blog/why-ai-is-paused/ canonical: https://www.insulin.dev/blog/why-ai-is-paused/ type: Blog description: "The four reasons Insulin pauses AI, why they run in a fixed order, what keeps working in each case, and the three costs that surprise people." --- # Why Insulin Paused AI, and How to Fix Each Case > Canonical HTML version: https://www.insulin.dev/blog/why-ai-is-paused/ 1. [Home](/) 2. / 3. [Blog](/blog/) 4. / 5. AI Is Paused: Which of the Four Reasons, and the Fix # AI Is Paused: Which of the Four Reasons, and the Fix Insulin names the reason it stopped, because each one has a different fix. Adding credit will not clear a limit you set yourself — and that is the most common wasted support ticket. ![Max Ma](/authors/max-ma.jpg) Max Ma Sep 13, 2026 ![AI Is Paused: Which of the Four Reasons, and the Fix](/images/blog/why-ai-is-paused/hero.png) Explore AI Summary [![](/logos/company/openai.svg)](https://chat.openai.com/?q=Read%20and%20summarize%20https%3A%2F%2Fwww.insulin.dev%2Fblog%2Fwhy-ai-is-paused%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Workspace. "Summarize with ChatGPT")[![](/logos/company/anthropic.svg) ](https://claude.ai/new?q=Read%20and%20summarize%20https%3A%2F%2Fwww.insulin.dev%2Fblog%2Fwhy-ai-is-paused%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Workspace. "Summarize with Claude")[![](/logos/company/gemini.svg)](https://www.google.com/search?udm=50&aep=11&q=Read%20and%20summarize%20https%3A%2F%2Fwww.insulin.dev%2Fblog%2Fwhy-ai-is-paused%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Workspace. "Summarize with Gemini")[](https://www.perplexity.ai/search/new?q=Read%20and%20summarize%20https%3A%2F%2Fwww.insulin.dev%2Fblog%2Fwhy-ai-is-paused%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Workspace. "Summarize with Perplexity") Table of Contents - [The four reasons, and what each one takes](#the-four-reasons-and-what-each-one-takes) - [Why the order matters](#why-the-order-matters) - [What keeps working](#what-keeps-working) - [Three costs that surprise people afterwards](#three-costs-that-surprise-people-afterwards) - [Preventing it instead](#preventing-it-instead) - [Frequently asked questions](#frequently-asked-questions) - [Takeaways](#takeaways) _A banner saying “billing problem” sends everyone to support. Insulin names which of four reasons applies, because the fix is different in each case — and one of them is not fixed by paying._ * * * When Insulin refuses a request for a billing reason, it says why. That is a deliberate design choice rather than a courtesy: a generic failure would route every case to the same place, and only one of the four actually needs support. The reason appears as a banner at the top of **Settings → Billing**, and in the conversation itself if you were chatting when it happened. ## The four reasons, and what each one takes Banner Why The fix This organization is suspended An administrative hold placed by Suger Contact support Monthly spending limit reached The month’s spend hit the limit **you** set Raise or remove the limit, on the same page AI features are paused — your credit has run out Pay as you go, and the balance reached zero Add credit All billable features are paused — your account has reached its debt limit The balance fell past the negative floor set for the account Add credit; contact support to change the floor **Two of these are yours to fix in under a minute. One is not fixable by paying at all.** ## Why the order matters They are evaluated in a fixed order, and you are told about the first that applies. That is not an implementation detail. Telling somebody their credit ran out when they are actually suspended sends them to top up an account that will still refuse them — money spent, problem unchanged, and a support ticket anyway. Ordering the checks and reporting only the first is what makes the banner actionable instead of merely accurate. **The trap inside that order: adding credit does not clear a limit you set yourself.** If the month’s spend hit your own monthly ceiling, the balance is irrelevant — topping up changes nothing, and the banner will still be there afterwards. Raise or remove the limit on the same page instead. This is the single most common wasted step, and it is wasted precisely because “add credit” is the intuitive response to any billing banner. **Monthly billing is never stopped for a balance.** On an invoiced account the invoice comes after the usage, so a negative balance is the normal state between invoices. Such an account can still be stopped by a suspension or by its own spending limit — but not by the number. ## What keeps working This is what people ask first, and the answer is deliberate: **losing access to your own work over a few cents is not an acceptable billing outcome, and paying afterwards does not give back the hours you could not work.** Stored files stay available. Running sandboxes keep running. What stops is new AI work — and, past the debt limit, new sandboxes and uploads as well. ## Three costs that surprise people afterwards Once the banner is cleared, the next question is usually why the spend got there. Three behaviours account for most of it, and none is obvious: **A stopped sandbox still costs storage.** Processor and memory are billed while a sandbox runs. **Storage is billed for as long as the sandbox exists** — running or stopped. Stopping one pauses two of its three meters, not three. **Object storage bills the month’s peak, not its end.** Deleting files late in the month does not retroactively reduce that month’s storage line. **AI called from inside a Custom App is metered like any other AI.** When a Custom App calls a model at runtime, those tokens are priced exactly as a chat turn’s are. If your organization has no model such a call can run on, the call is refused with _“No usable model provider configured”_ rather than silently returning nothing. Worth knowing alongside those: cached context is counted in full, reasoning tokens count as output, and a request that fails partway is still billed — the provider ran it and charged for it whether or not the answer reached you. ## Preventing it instead Three controls on **Settings → Billing** belong to your organization: the payment method on file, the monthly spending limit, and automatic top-up. **You do not need a payment method to use Insulin.** The monthly free credit is spendable without a card, and most accounts never add one. Add one when you want automatic top-up, or when you are moving to monthly billing — and note that card details are entered on Stripe’s own hosted page, never in the Suger console, which stores a reference to the method rather than the number. Automatic top-up is the control that actually prevents the pause. A spending limit is the control that causes one deliberately, which is the point of having it. For how the meters themselves work — the six resources and what is never billed — the [pricing breakdown](/blog/per-seat-vs-usage-based-ai-pricing/) covers it. ## Frequently asked questions ### Why did adding credit not restart my AI? Because the pause was your own monthly spending limit, not the balance. The limit is checked before the balance, and money does not clear it — raise or remove the limit on **Settings → Billing**. ### Do I lose my files when AI pauses? No. Stored files remain available and running sandboxes keep running. What stops is new AI work, plus new sandboxes and uploads once an account is past its debt limit. ### Does a stopped sandbox still cost anything? Yes — storage. Processor and memory are billed only while a sandbox runs, but storage is billed for as long as the sandbox exists, stopped or not. ### Can an invoiced account be paused for a negative balance? No. Monthly billing is never stopped for a balance, because the invoice follows the usage. It can still be stopped by a suspension or by its own spending limit. ### Do I need a card to use Insulin? No. The monthly free credit is spendable without one. A payment method is needed for automatic top-up or to move to monthly billing, and it is entered on Stripe’s hosted page rather than in the Suger console. ## Takeaways - Four reasons, four different fixes — read which one the banner names before acting. - **Adding credit does not clear a spending limit you set.** That is the common wasted step. - Files and running sandboxes survive every pause; that is by design. - A stopped sandbox still bills storage, and object storage bills the month’s peak. - Automatic top-up prevents the pause; a spending limit causes one on purpose. ## Sources Primary sources for the platform rules cited above. Last verified September 13, 2026. Cloud providers change fees, eligibility, and program terms without notice — check the source before relying on a figure. - [Suger docs: When AI Pauses](https://doc.suger.io/insulin/billing/when-ai-pauses/) — The four reasons, their evaluation order, and what keeps working in each case - [Suger docs: Payment, Limits, and Top-Ups](https://doc.suger.io/insulin/billing/spend-controls/) — The three controls an organization owns: payment method, monthly spending limit, automatic top-up - [Suger docs: What Is Metered](https://doc.suger.io/insulin/billing/metering/) — Sandbox storage billed while stopped, and AI called from a Custom App metered like any other AI ## Keep reading - [TrustEdit What Your AI Assistant Remembers About YouSep 19, 2026](/blog/edit-what-your-ai-assistant-remembers/) - [AgentsOne Thread, Many Agents: How Channels WorkSep 10, 2026](/blog/channels-multi-agent-threads/) - [WorkspaceHow to Keep a Long-Running AI Task on TrackSep 10, 2026](/blog/keep-a-long-ai-task-on-track/) - [TrustWho Picks the Model, and What If It Fails?Sep 10, 2026](/blog/who-picks-the-model/) [Browse every post on the Insulin Blog](/blog/) ### Stay Updated Get the latest Cloud GTM insights, product updates, and marketplace strategies delivered to your inbox.