ferraus jobs result
The JSON result envelope of a finished job
Synopsis
ferraus jobs result <id> [options]
What it does
The JSON result envelope of a finished job
Examples
The finished job's result envelope, exactly as the command would have printed it
ferraus jobs result 1760873452123-3f2a
The envelope as JSON (outputs, metrics, warnings)
ferraus jobs result 1760873452123-3f2a --json
Just the files the job wrote
ferraus jobs result 1760873452123-3f2a --json | jq .outputs
Options
| Flag | Type | Default | Meaning |
|---|---|---|---|
<id> | text | — | Job id Required. |
Global options
Every command also accepts the global options (-o, --json, --dry-run, --overwrite, --progress, ...). See Global options.
Exit codes
| Code | Meaning |
|---|---|
| 0 | Success |
| 1 | Processing failed |
| 2 | Usage or parameter error |
| 3 | Input missing or unreadable |
| 8 | Cancelled |
| 70 | Internal error (bug) |
Common mistakes
- Expecting human-readable text when scripting: add
--jsonfor a stable machine result.
For models
- MCP tool:
ferraus_jobs_result - Schema:
ferraus schema jobs result - Pipeline:
{ op: jobs result, args: { ... } }(flag names with_instead of-) - fx stage: no
{"command": "jobs result", "defaults": {}}