get_cloudflow_flow_run
Retrieve a CloudFlow run's status and per-node input/output JSON to diagnose why a run failed or produced wrong data.
Instructions
Manage CloudFlow. Returns a run's status and, for each node, the JSON it consumed and produced. This is how you find out why a run failed, or that it "succeeded" while producing the wrong data.
input is null for most node types, and that is not an error. Only action nodes — the
AWS, GCP, Azure, Oracle, DoiT and admin operations — record their inputs. Transform, code,
branch, switch, datastore, subflow and trigger nodes record none, so their input is
always null. output is recorded by every node that finishes, so read a transform's
behaviour from its output.
Payloads appear as soon as a node reports a terminal status, so a poll loop can read results while later nodes are still running.
Any value the node's schema marks sensitive is replaced with a redaction marker; credentials and connection configuration never appear.
Each input and output is capped at 64KB. When a payload exceeds that, whole entries
are dropped from the end, truncated is true, and totalBytes reports the untruncated
size — nothing is silently cut, and what you receive is always valid JSON.
Runs belonging to another tenant, or to a different flow, return 404. Nodes inside a
fan-out currently report only the last path to finish.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| runId | Yes | ||
| flowId | Yes | ||
| customerContext | No | Scope the request to a specific customer by ID. Required for DoiT employees (whose token isn't tied to a single customer); omit for direct customer users. |