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
Max Ma
Sep 13, 2026 ·

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.

Updated November 18, 2026: this post now says what a pause does to jobs, goals, knowledge-base indexing and the Fours console’s AI features, and that past the debt limit knowledge-base uploads and website syncs are refused too. It also corrects how cached context is priced: at cache rates of its own, not in full.


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

BannerWhyThe fix
This organization is suspendedAn administrative hold placed by FoursContact support
Monthly spending limit reachedThe month’s spend hit the limit you setRaise or remove the limit, on the same page
AI features are paused — your credit has run outPay as you go, and the balance reached zeroAdd credit
All billable features are paused — your account has reached its debt limitThe balance fell past the negative floor set for the accountAdd 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.

New AI work is more than chat. The check sits on every path that calls a model for your organization, and Fours’ When AI pauses page says what each one does when it is refused:

  • A job run that is refused ends Failed, with the reason as its error.
  • A goal that is refused stops, and stays stopped until someone starts it again.
  • A knowledge-base document whose indexing is refused fails with the reason, and is not retried on its own: index it again once AI is back. While only AI is paused, files and pages can still be added, but indexing them needs AI, so they can’t be searched until AI is back and they are indexed again.
  • The Fours console’s AI features, such as co-sell scoring, marketplace insights, document extraction and workflow AI steps, have no conversation to answer in, so the call fails with the same reason instead.

Past the debt limit, the uploads that stop include files added to a knowledge base, whether you upload or paste them or an agent saves them. A website sync stores the pages it crawls, so it is refused too: the website’s row turns Failed with the reason.

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 billed as input tokens at cache rates of its own (reading from the cache costs 10% of the model’s input price and writing to it 125%, unless the supplier publishes its own cache price for that model), 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 Fours 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 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, uploads and website syncs 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 Fours 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 November 18, 2026. Providers change their products, prices and terms without notice — check the source before relying on a detail.

  • Fours docs: When AI Pauses — The four reasons, their evaluation order, and what keeps working in each case; a refused request on every path that calls a model: a job run ending Failed with the reason as its error, a goal stopping and staying stopped until someone starts it again, a document whose indexing is refused failing and not being retried on its own, and a call with no conversation to answer in, such as the console's other AI features, failing with the same reason; past the debt limit, knowledge-base uploads refused and a website sync refused, its row turning Failed with the reason
  • Fours docs: Payment, Limits, and Top-Ups — The three controls an organization owns: payment method, monthly spending limit, automatic top-up
  • Fours docs: What Is Metered — Sandbox storage billed while stopped; AI that an app runs billed like any other AI; cached context recorded as input tokens and priced at rates of its own, reading from the cache at 10% of the model's input price and writing to it at 125% unless the supplier publishes its own cache price; reasoning tokens as output; failed and cancelled requests still billed

Browse every post on the Insulin Blog

Stay Updated

New posts, product updates and marketplace strategy are shared on LinkedIn as they publish.

Follow Fours on LinkedIn