Skip to content
Evergrowth Documentation

A run stopped because a credit limit was reached

A run that stops on a credit limit has not failed. It paused, kept everything it had already produced, and is waiting for either the next window or a bigger ceiling. The one thing worth getting right is which ceiling stopped it, because the fix is different for each - and for all but the workspace balance, buying credits does nothing.

Symptom

Section titled “Symptom”

One of these, depending on where you are looking:

  • A task in the feed carries a User limit reached or Team limit reached label where a run out of workspace credits would say Out of credits, and its progress chip reads the same way, for example User limit reached at 12/40. Opening it shows a banner such as “User limit reached - this run stopped because you reached your personal credit limit” or “Team limit reached - this run stopped because your team (Sales EMEA) reached its credit limit”, with the name of your team in brackets.
  • The task’s own view says “This workflow was stopped because you reached your personal credit limit” (or “…because your team reached its credit limit”), with no Top-up link beside it.
  • A task labelled Workflow limit reached stopped on the credit limit set on that run itself. Its view says “This workflow was stopped because this workflow reached its own credit limit”, and it offers Raise limit & continue and Remove limit & continue rather than Continue workflow.
  • On a run a colleague launched, the wording names them by email instead of saying “you”: “…because [their email] reached their personal credit limit” or “…because [their email]‘s team reached its credit limit”. The limit that stopped it is theirs, not yours.
  • A notification arrives titled Paused, saying the run “was paused because you reached your personal credit limit” or “because your team reached its credit limit”. Clicking it opens the run in the task feed.
  • The credits control in the top header reads Limit reached under Your limit or Team limit, and the pill beside it names that limit rather than the workspace, for example “you: 0% left”.
  • Asking Eva something returns “Eva can’t make tool calls right now.” She then names which ceiling it was. Your own limit reads “You’ve reached your credit limit for this period, so this request was not run. It resumes when the limit resets, or a workspace admin raises it,” with no button beneath it, because buying credits would not help. The workspace balance instead reads “Your workspace has 0 credits, so this request was not run. Top up and send it again,” with a Buy more credits button. Nothing was run either way, so nothing was charged; the same wording appears in the Slack thread when you asked her there.

The Out of credits label, with wording that names your workspace - “[your workspace] ran out of credits” - and a Top-up link, is a different situation - the shared workspace balance, not a limit. That one is fixed by buying credits: see Top up credits.

Why this happens

Section titled “Why this happens”

Four separate ceilings can stop a run, and any one of them is enough:

What stopped itWhat the wording saysWho can clear it
Your personal credit limit”you reached your personal credit limit”An admin raises or removes your limit, or the window resets
Your team’s credit limit”your team reached its credit limit”An admin raises or removes the team’s limit, or the window resets
The workspace credit balance”[your workspace] ran out of credits”Anyone who can buy credits, by topping up
The run’s own credit limit”this workflow reached its own credit limit”Anyone who can launch workflows, by raising or removing that run’s limit

The run’s own limit is the simplest of the four: somebody typed a credit ceiling for that one run when they launched it (or on a scheduled automation’s per-run cap), and the run reached it. See Cap what a run can spend.

A personal or team limit is a cap somebody set deliberately on how much you or your team may spend in a week or a month. It is not related to how many credits the workspace has left - a workspace with plenty of balance will still stop a capped person who has spent their share. Credits and billing explains the model; Manage your team and permissions covers changing a limit.

Two details explain most of the confusion:

  • Limits reset on the calendar. A weekly limit reopens at the start of the week and a monthly one at the start of the month, so waiting is a real fix with a knowable date. The workspace tells you that date next to each limit.
  • Eva is stopped before she starts, not partway. A workflow pauses mid-run and keeps what it produced; a question to Eva is refused outright at the point you send it, so there is nothing part-finished to resume. Once the ceiling has room, send the question again.
  • The stop is prompt rather than exact. Spend is measured as runs complete, so a cap stops work once you have gone over rather than at the precise credit. A run that started just under the line can finish slightly past it. That is expected, not a billing error.

How to fix it

Section titled “How to fix it”
  1. Read which limit it was. The label on the task already says it - User limit reached, Team limit reached, Workflow limit reached, or Out of credits. Open the paused task from the task feed and read the banner for who it applies to, or open the credits control in the header and see which section reads Limit reached - Your limit, Team limit, or Workspace limit. Everything below depends on this.
  2. If it is the workspace balance, top up. See Top up credits. This is the only one of the three where buying credits helps, which is why the paused-run banner shows a Top-up link for it and not for the other two.
  3. If it is the run’s own limit (Workflow limit reached), decide whether the rest of the run is worth the spend. If it is, select Raise limit & continue and set a higher amount - it must be above what the run has already used, and should leave room for the work still to do, because each step needs space for its full possible price before it starts - or Remove limit & continue. If it is not, leave it paused: everything it finished is kept. See Resume a run that stopped for credits.
  4. If it is your own or your team’s limit, check when it resets. The header credits control shows the reset date for each limit. If that is soon and the work is not urgent, waiting costs nothing - the run keeps its progress in the meantime.
  5. If you need it sooner, ask an admin to raise the limit. Anyone who can manage users can change a person’s limit, and anyone who can manage teams can change a team’s; both are done from Settings, then Users management. Tell them which limit and which period stopped you, so they change the one that is actually binding.
  6. Continue the run once the limit has room again. Open the paused task in the task feed and select Continue workflow (it needs the access that lets you launch agents and workflows in the first place). Continuing is checked against the limits at that moment, so an attempt made before the limit is raised or reset pauses again straight away - get the ceiling changed first, then continue.
  7. Where the same cap keeps stopping the same work, treat it as a budgeting question rather than an obstacle. A limit that binds every week is either set too low for that person’s book of business, or the work behind it belongs on a scheduled run, which draws on the workspace balance rather than on a person’s cap.

Scheduled runs, file imports, and integration-triggered work have no person behind them, so personal and team limits never stop them - if one of those paused, it was the workspace balance, or, for a scheduled automation with a Never spend more than cap, that run’s own limit.

Eva: distinguish the three causes before advising anything, because the advice is the opposite for two of them. Company balance exhausted: label Out of credits, wording ” ran out of credits” (older runs and other surfaces may still say “your company”), fix is a top-up. Personal cap: label User limit reached, wording “you reached your personal credit limit”. Team cap: label Team limit reached, wording “your team () reached its credit limit”. Before October 2026 both caps showed a plain Limit reached label. Fourth cause, the run’s own per-run limit: label Workflow limit reached, wording “this workflow reached its own credit limit”; nobody’s personal limit and no top-up is involved, and the only fix is raising (above what the run already used) or removing that run’s limit from the paused task, which continues it in the same step - there is no separate Continue workflow click. The per-run limit is a hard cap, so a run stopped by it ends at or a little below the limit, never above it; a run that paused again right after a small raise had no room for its next step’s maximum price. When the run was launched by someone else, the wording names that person by email, and the binding cap is theirs - the viewer’s own limits are irrelevant to it. For the latter two a top-up changes nothing - the fix is a raised limit (an admin, from Settings, then Users management) or the next calendar window (weekly resets at the start of the week, monthly at the start of the month). The button is labelled Continue workflow and re-checks the caps at the moment it is clicked, so tell the user to get the limit raised first and only then continue, otherwise the run pauses again at the first step. A paused run keeps its completed work; nothing needs re-launching from scratch. If the user’s own header shows no personal or team limit at all, they are uncapped and the cause must be the workspace balance.

Eva: when the block is you, the two cases are worded differently on purpose and the difference is the whole advice. Your own message names the workspace balance and offers a top-up button; the personal-limit message offers no button, because a top-up refills a pool that was never the problem. Never suggest buying credits for the limit case. A refused turn ran nothing and cost nothing - there is no partial answer to recover and no “continue” to click, so the honest instruction is simply to re-send once the limit resets or is raised. This applies identically in Slack.

Section titled “Related”