A budget paused my run
Why a run shows Paused · budget, which limit stopped it, and how to approve more once, raise the limit, wait for the reset or stop.
On this page
Duun never stops a run in the middle of a step to save money. When a run reaches a spending limit, it finishes the step it’s on, then pauses and asks. While it waits, it keeps its worktree and stops machine time, so the pause itself costs nothing.
Symptoms
- The run shows Paused · budget.
- An ask in your Inbox reads Decide whether it keeps going.
- New runs in a project or factory wait with Waiting · budget instead of starting.
- A banner says credits are used up and runs are paused.
Find out which limit stopped it
Open the run and click its cost meter in the header. It shows what the run has spent, and Paused by names the exact limit, for example the workflow’s per-run budget, the factory’s daily budget, or the workspace’s monthly budget. Also capped by lists the other limits that apply.
The lowest remaining limit always wins, so raising a different one won’t help.
Likely causes and fixes
A budget was reached
Choose one of these from the Inbox ask or the cost meter:
| Option | What it does | Who can use it |
|---|---|---|
| Approve +$X once | Raises the limit for this run only | Anyone who can approve in the project |
| Raise limit… | Edits the budget; every run it held resumes | Admins, or factory admins for their factory’s budgets |
| Wait for reset | The run resumes on its own when the daily or monthly period resets | Anyone |
| Stop run | Cancels the run with a summary of what it did | Anyone who can approve in the project |
- Open the ask in your Inbox, or the run’s cost meter.
- Check Paused by to see which limit applies.
- Choose Approve once (Approve +$X once on the cost meter) to let this run continue, or Raise limit… to change the budget for every run. The run resumes from the step it paused at.
If you can’t change the limit yourself, you’ll see Ask an admin, which sends the request to the people who can.
The workflow’s per-run budget is too low
If the same workflow keeps pausing, its Budget per run may not fit the work. Raise it in the workflow’s Limits, or change Pause and ask at so it asks later. Saving writes a new workflow version; runs in progress keep theirs. See Limits and budgets.
Credits ran out
If the banner says Credits used up · runs paused, the workspace has no included usage or prepaid credits left. An admin or billing member can click Buy credits, then resume the paused runs. See Credits and automatic recharge.
Prevent it next time
- Check the estimate before you start a run: it’s based on that workflow’s past runs.
- Set alert thresholds below 100%, such as 50% and 80%, so you hear about it early. See Budgets and alerts.
- Turn on automatic recharge so credits don’t run out.
- Use a cheaper model for simple steps, or your own model keys, which Duun doesn’t charge for.
Still stuck? Contact support with the run id and the budget named under Paused by.