Budget exceeded

A spend was refused because it would exceed the agent's remaining periodic budget for the current period.

#Symptom

A spend is refused even though it's within the per-transaction limit, and the refusal indicates the periodic budget is the reason.

#Why this happens

An agent's periodic budget is a cumulative cap over a recurring time window. Every spend the agent makes in the current period counts against it; once exhausted, further spends are refused until the period rolls over — even if the vault's overall balance is plenty large and even if this single spend would be well within the per-transaction limit.

#Checking how much budget remains

The vault's dashboard page shows the remaining budget for the current period. You can also simulate a spend to get an exact, authoritative answer before attempting it for real.

#Waiting for rollover

The period rolls over automatically once Kaspa's own consensus DAA score has genuinely advanced past the period's committed boundary — this is enforced by the covenant itself, not a date the application decides. You do not need to do anything to trigger it; the next spend attempt after the boundary is evaluated against a freshly reset budget. If you need to know approximately when that will be, the vault's period-start and period-length fields (visible via the API/SDK) let you estimate it, though the exact rollover point is defined in DAA score, not wall-clock time.

#If the budget is genuinely too low for legitimate use

The periodic budget is owner-configured and can be changed — see Set a periodic budget. This is an owner-signed covenant operation; an agent or approver cannot raise its own budget.

See also: Periodic budget, Per-transaction limit.