feature

Budget exceeded

Your script hit a processing budget — Chartnaut stopped or warned so the Terminal (or study run) stays responsive.

Work through the checklist to reduce per-bar or per-event work, drop unused dependencies, or iterate on a smaller range.

Typical messages

  • budget_wall_clock

  • too_many_event_timeouts

  • Generic “budget” / timeout warnings in the builder

Fixes (in order)

  1. Smaller range while iterating (Collect / study run / dry-run lookback).

  2. Less work per event/bar — shorter candles.forward, fewer series, avoid nested loops.

  3. Drop unused dependencies — each dep multiplies cost.

  4. Narrow runOn so the script is not evaluated on inappropriate timeframes.

  5. Re-lint, re-run, then snapshot when lean.

Not the same as

  • Broker Capacity

  • AI credits

  • Network / broker disconnects

Next

  1. Budgets and limits

  2. Study API