Skip to content

Budgets constrain admission of new chargeable work. Use them alongside the Workspace credit balance and usage records to keep experimentation and ongoing operation within the limits you intend.

A budget is a control on work, not a separate balance. Setting a higher budget does not purchase credits or authorize access to a resource.

Choose the right scope

Review Workspace Budgets and the controls available for the relevant Agent, Project, or production scope. Chats inherit Workspace funding and policy; the Chat surface does not provide an independent persistent budget setting.

  1. Identify the work and Workspace that will pay for it.
  2. Inspect recent usage or begin with a small representative task.
  3. Set the applicable limit and period in the owning budget controls.
  4. Monitor consumption and adjust deliberately as the workload changes.

Understand what a limit does

ConditionMeaning
Budget available, insufficient fundingFunding checks can still prevent execution.
Credits available, budget reachedNew work can be blocked by the budget.
External customer-funded providerThat provider's own charges need separate controls.
Work already in progressAdmitted work and running services can continue.

Budgets do not guarantee zero overshoot. Reservations, in-flight work, and running production services can make final usage differ from the amount visible when you set a limit.

Investigate unexpected consumption

Start with Usage, identify the responsible resource and service, and check whether work remains active. Changing a future budget does not undo a completed charge or stop every existing workload. Use the resource's supported stop or lifecycle action when that is the intended outcome.

Review both development and production when a Project has associated Sites. A quiet development conversation does not mean its production destinations have stopped running.

Example: bound an experiment

Before running several variations of a report, inspect a small representative run and choose the supported budget scope and period. Monitor the experiment as it proceeds instead of treating the limit as a promise that all active work stops at an exact amount.

If the intention is to stop a running task, use its Messaging controls. For production services, use the appropriate Site operation.

Example: funding exists but work cannot start

A Workspace may have credits remaining while the applicable budget has been reached. Check the budget's scope and period before purchasing more credits. Conversely, raising the budget will not resolve insufficient funding. Use the reported reason and Credits view to identify which control applies.