reference

Budgets and limits

Chartnaut caps how much work a script can do so a heavy loop cannot freeze the Terminal or a study run.

If you see a budget warning or timeout, this page explains what was protected and how to slim the script — fewer deps, less work per bar/event, or a smaller range while you iterate. Budgets are not AI credits or Broker Capacity.

What budgets protect

Indicator processing on live and historical charts
Definition / flow runs over long lookbacks
Study runs over large event sets
Nested dependencies that multiply work (indicator → definition → study)

Study runtime (typical caps)

Limit	Behavior
Wall clock — client soft ~2m / hard ~10m	`budget_wall_clock`
Wall clock — backend soft ~8m / hard ~10m	`budget_wall_clock`
Per-`onEvent` ~15s	Event timeout
≥10 event timeouts	`too_many_event_timeouts`

Flow / indicator runs have their own timeouts. Exact numbers can move — treat product errors as source of truth.

What to do when you hit a limit

Read the warning or error in the builder.
Reduce work per bar / per event — fewer series, leaner loops, narrower forward windows.
Drop unused dependencies.
Collect or run on a smaller range while you iterate.
Snapshot again after the script is lean.

Budgets ≠ Broker Capacity ≠ AI credits.

← Previous Next →