invalid_workflow
invalid_workflow
Section titled “invalid_workflow”HTTP status: 400 Bad Request
How to fix
Section titled “How to fix”- Validate the JSON syntactically. Run
cat workflow.json | jq .first — half of these failures are stray commas, missing brackets, or duplicate keys. - Confirm every node ID is unique inside the
nodesarray. Two nodes with the sameidget rejected. - Confirm the graph is acyclic. Every workflow must terminate. A cycle (node A → B → A) fails DAG validation.
- Confirm every
edges[].sourceandedges[].targetmatches an existing node ID. Dangling edges fail. - Confirm exactly one
entrynode exists and it has no incoming edges. The DAG must have a single entry point.
What this means
Section titled “What this means”The workflow JSON parsed but failed our structural validator. We require a directed acyclic graph with a single entry node, unique node IDs, and edges that reference existing nodes. Failures here happen before any URL is dispatched.
Related errors
Section titled “Related errors”invalid_input— generic field-level validation for non-workflow fieldsnode_type_unknown— workflow shape is valid but uses an unrecognized node typeworkflow_disabled— workflow is valid but paused
Still stuck?
Section titled “Still stuck?”Contact support with your request_id (looks like req_01HF3JKB...). Include the workflow JSON so we can reproduce the validation failure.