oz0 job why
Usage and flags for oz0 job why.
For: Operators and developers looking up a command.
Answer "why is this job waiting?" in plain words: its open steps, the queues they wait on and the nodes that could take them, approvals waiting for a person, a spent budget, a rate limit or a retry, and what its child jobs wait for.
A harness session lost with its node is named too: the node, how long it ran and what it spent, and whether a fresh session started from the job's input or waits for a person's restart approval.
Usage
oz0 job why JOB [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--json | bool | print JSON instead of a table | |
--tenant | string | default | tenant |
Inherited flags
| Flag | Type | Default | Description |
|---|---|---|---|
--context | string | $OZ0_CONTEXT or <config dir>/orchestrator-zero/context.json | CLI context file written by server init |
--log-level | string | info | log level: debug, info, warn or error |
See all oz0 commands and the global flags.