Parents and children, linked.
The parent/child dependency commands behind FlowProducer: legacy parent linking, child failure values, and removing a child dependency or the unprocessed children.
Part of the TCP protocol reference, which describes the framing, authentication, pipelining and response format that every command on this page uses.
The atomic graph commit, PUSHF, is documented with the job commands. Child return values are read with GetChildrenValues, and an active job parks for its children with MoveToWaitingChildren.
Flow Dependency Commands
Section titled “Flow Dependency Commands”Used by FlowProducer for parent/child job graphs.
UpdateParent
Section titled “UpdateParent”Request: { cmd: 'UpdateParent', childId: string, parentId: string }
Response: { ok: true }
This is a compatibility command for legacy multi-request flow creation. If the
parent already declares childId, only the child’s temporary parent marker is
updated; the parent may be active or terminal and its state/topology is not
rewritten. A queued, active, completed, DLQ, or removeOnComplete-tombstoned
child is accepted when that declared edge is consistent. Persisted job/DLQ data
and any failure-outbox key move atomically. A genuinely new edge still requires
a queued parent; conflicting ownership, self-links, and undeclared missing
nodes fail.
GetFailedChildrenValues
Section titled “GetFailedChildrenValues”Request: { cmd: 'GetFailedChildrenValues', id: string }
Response: { ok: true, values: Record<string, any> }
GetIgnoredChildrenFailures
Section titled “GetIgnoredChildrenFailures”Request: { cmd: 'GetIgnoredChildrenFailures', id: string }
Response: { ok: true, values: Record<string, any> }
RemoveChildDependency
Section titled “RemoveChildDependency”Request: { cmd: 'RemoveChildDependency', id: string }
Response: { ok: true, removed: boolean }
RemoveUnprocessedChildren
Section titled “RemoveUnprocessedChildren”Request: { cmd: 'RemoveUnprocessedChildren', id: string }
Response: { ok: true }