orion-cli traces
Views execution traces.
Synopsis
orion-cli traces <list|get|wait> [args] [flags]
Description
Reading a trace needs either an admin credential or the per-submission
trace token that the async 202 returns alongside the id. Pass it with
--token <token> on get and wait. Without one, any caller who guessed an
id could read another caller’s payload.
Subcommands
| Subcommand | Description |
|---|---|
list | List traces; filter with --status, --channel, and --mode. Sorts by created_at, updated_at, status, channel, mode. |
get <id> | Show trace details, including the result or error. |
wait <id> | Poll until the trace completes. --interval <secs> (default 1), --timeout <secs> (default 60). Exit codes: 0 completed, 1 failed, 2 timeout. |
Options
list has two paging controls beyond --limit / --offset:
| Flag | Description |
|---|---|
--cursor <c> | Keyset cursor from a previous page’s next_cursor; pass it back unmodified. Valid only with the default created_at ordering, mutually exclusive with --offset, and cheaper on a large table because it never skips rows. |
--include-total | Ask the server to compute total. Off by default: the count is a full scan of the filtered set. |
Examples
orion-cli traces list --status failed --channel orders
Related
- Traces and async processing: what a trace holds and how it is stored.
- Data API › Trace endpoints: the routes and the trace token.
orion-cli dlq: the traces that failed to persist.orion-clicommands: everyorion-clisubcommand.
Last verified 14 September 2026