mxr send-outcome
Generated from
mxr send-outcome --help. Edit the clap definitions incrates/daemon/src/cli/and re-runnpm run buildinsite/to regenerate.
Inspect a send operation after disconnect, including after draft cleanup
mxr send-outcome [OPTIONS] --account <ACCOUNT> <OPERATION_ID>Arguments
Section titled “Arguments”| Flag | Description |
|---|---|
<OPERATION_ID> |
Options
Section titled “Options”| Flag | Description |
|---|---|
--expected-workspace <EXPECTED_WORKSPACE> |
Original workspace JSON retained with the send review |
--account <ACCOUNT> |
|
--format <FORMAT> |
[possible values: table, json, jsonl, csv, ids] |
-h, --help |
Print help |
Use When
Section titled “Use When”Query the durable outcome with the workspace JSON retained from the original send preview. Do not infer a new owner after reconnect; unknown is not permission to retry.
Everyday Examples
Section titled “Everyday Examples”mxr send-outcome OPERATION_ID --account ACCOUNT_ID --expected-workspace '<OWNER_JSON_FROM_ORIGINAL_PREVIEW>' --format jsonmxr send-outcome 'draft:DRAFT_ID' --account ACCOUNT_ID --expected-workspace '<OWNER_JSON_FROM_SCHEDULE_PREVIEW>' --format jsonSee also
Section titled “See also”- CLI overview: full command index
- Concepts: query operators, search modes, JSON shapes
- Automation contract: which commands support
--format json,--dry-run, stdin