flow_invalid

A conversation flow failed validation and was not saved.

• A node references a step that does not exist.
• The graph has a cycle, or an unreachable branch.
• A required field on a node is absent.

• Read `details` — every problem is reported at once, not one per save. A fifteen-node flow would otherwise be fifteen round trips.
• Fix them together and resubmit.

This code carries a details object with more than the message can say:

{
  "error": {
    "code": "flow_invalid",
    "message": "A conversation flow failed validation and was not saved",
    "details": { ... },
    "request_id": "7cb7f7862a82425d8e4c3fb8a497dfe6"
  },
  "type": "https://integrable.cloud/docs/errors/flow_invalid",
  "title": "Flow Invalid",
  "status": 422,
  "detail": "A conversation flow failed validation and was not saved",
  "instance": "/api/bots/01a0652b-3713-7ea1-a6c9-2e895389ec34"
}

Branch on error.code, not on the message — the code is stable, the sentence is not. Log request_id either way.

Codes that are easy to confuse with this one, or that show up alongside it:

• validation_error

Quote the request_id from the response — hello@integrable.cloud. It is what lets us find the exact request. The full list of codes is at Error codes, and the conventions every endpoint shares are in Retries, versioning and limits.