Require a real trace UUID
The current inventory is empty. This lesson never inserts a fabricated identifier merely to make a detail command render.
Separate lifecycle from delegation
The mission moved through running, paused, and cancelled. Its handoffs, tokens, and tool calls stayed at zero. Lifecycle state does not prove delegation.
Read the current inventory
armaraos orchestration list --limit 20
armaraos orchestration list --limit 20 --json
The empty array matches the empty mission handoff list.
Use only an ID from the inventory
armaraos orchestration trace <TRACE_ID>
armaraos orchestration trace <TRACE_ID> --jsonA trace UUID comes from a populated list. No row means no valid detail command to run.
Keep four views distinct
| View | Meaning |
|---|---|
| trace | Every recorded event in order. |
| tree | Who delegated to whom. |
| cost | Token and cost rollup. |
| live | Snapshot of an active trace. |
Diagnose emptiness in order
- Read mission handoffs and token stats.
- Recheck quota on the owner UUID.
- Run doctor and inspect logs.
- Check provider concurrency and rate limits.
Protect populated traces
A future trace can contain prompt text and returned content. Read and redact before sharing it.
Check it / reconcile two empty views
Explain why no trace ID exists.
Run the JSON list and connect its empty array to the mission's empty handoff and zero-token detail.
Trace records can contain prompts, agent IDs, tool arguments, and returned text. Treat a future populated trace as sensitive operational data.
Troubleshooting for this sitting
| What you see | Likely cause | What to do |
|---|---|---|
| Trace list is empty | No delegation event was recorded. | Compare mission handoffs and stats. |
| Detail needs an ID | IDs come from a populated list. | Do not invent one. |
| Mission has a final state | That is lifecycle evidence. | Look for handoffs before claiming delegation. |
| A future trace has private text | Prompts or output were recorded. | Redact before sharing. |