Orchestration Runs

Account status — using account 5

• Window usage so far: 30,052,875 tokens ($24.63) — 304% of its own last observed ceiling
• Total dispatches on this account: 57

Phase Timeline¶

SHARED TOTAL: 4m, 79,388 tokens, $0.2696, 7 row(s) with no token data (rows 1–13)

Total Run Time: 41m (wall clock, 08-10-2026 18:33:22 → 08-10-2026 19:14:41 IST — not a sum of the per-side totals above, since sides overlap)
Active time: 4m | Waiting (session limits, approvals, dead sessions): 37m
Total Tokens Consumed: 79,388 (plus 7 row(s) whose usage was never captured — run execution_tracker.py enrich-audit to backfill. This is a floor, not the total.)
Token breakdown: input 2,582 · output 635 · cache-create 39,997 · cache-read 36,174 (46% of the total). Cache-read is context a node re-sends to itself across its own tool-use turns, billed at roughly a tenth of fresh input — a large Tokens number that is mostly cache-read is a long tool loop, not a large workload.
Total Cost: $0.2696 (plus 7 row(s) whose usage was never captured — run execution_tracker.py enrich-audit to backfill. This is a floor, not the total.)

Account status — using account 5

• Window usage so far: 30,132,263 tokens ($24.90) — 305% of its own last observed ceiling
• Total dispatches on this account: 58

Account status — account 5 hit its limit, switching away

• Reason: usage_limit
• Real usage at cutoff: 0 tokens ($0.00) — this becomes its new observed ceiling
• Cooling down until: 2026-10-08T15:26:20.832691+00:00
• Consecutive failures: 1