opschain changes link
Included from Basic tier
opschain changes link <id|code> <run-id> [--owner /|/projects/<code>]
Attaches a run that was created without naming its record after the
fact. The record must be approved, its scope must
hold the run's target — a workflow run's effective target, the one node all
its change steps target (opschain docs resources/change_record) — and the
run must be under no other record (unlink it there first); the record's
window does not bind a link. Audited as audit:change_record:linked on the run's chain;
the run's association reads linked. The nested runs the run has already
spawned, at every depth, join with it as inherited — as the ones it
spawns later do — each audited on its own chain with via_run_id; a nested
run under another record, or more than 1000 nested runs, refuses the whole
link by name. Needs read on the run and update on the record's
change_records rule path; an agent may link.
Flags
| Flag | Meaning |
|---|---|
--owner <path> | The record's owner, / or /projects/<code> — narrows a code two owners hold; ignored for an id. |
Exit codes
| Code | Meaning |
|---|---|
| 0 | Linked. |
| 1 | Refused — the record is not approved, the run is outside its scope or under another record, a nested run of it is under another record, or either was not found. |