Start from the trace inventory
No active or completed trace exists, so live-by-ID and export cannot be demonstrated honestly. Summary watch remains capture live.
Read the live-tool contracts
armaraos orchestration live <TRACE_ID> --json
armaraos orchestration watch
armaraos orchestration watch --trace <TRACE_ID> --interval-secs 3
Watch summaries, then stop
Watch has no JSON flag. With --trace, it needs a real trace UUID.
Read the budget value that exists
armaraos orchestration quota <AGENT_UUID> --json
The 0.0 field is a declaration, not evidence that ArmaraOS will halt spending.
Put enforcement in the right place
- Choose a cheaper or free model.
- Use compression where fidelity permits.
- Schedule in hours, not minutes.
- Set a hard paid-provider billing limit.
Export only a genuine trace
armaraos orchestration export <TRACE_ID> -o run.jsonExport already emits one JSON document. With no trace row, there is no honest run.json to produce.
Name the support artifact
A future run.json combines events, tree, and cost. Review and redact it before sharing.
Keep the limitation calm and exact
Budget caps do not provide proven enforcement in 0.8.3. Provider controls are the real ceiling.
Check it / find the declaration
Read 0.0 without calling it protection.
Run quota JSON, locate the cost field, and explain why the trace list must be checked before export.
Never build a procedure that assumes the 0.0 in-product budget field will halt a run. Use an enforcing provider limit and unscheduled small tests.
Troubleshooting for this sitting
| What you see | Likely cause | What to do |
|---|---|---|
| Live has nothing to show | No active trace exists. | Read the inventory first. |
| Watch keeps polling | It is interactive. | Stop with Ctrl+C. |
| Export needs an ID | No trace row exists. | Do not invent one. |
| Budget reads 0.0 | Current declaration. | Use provider controls for enforcement. |