Payload Limits - CloudCruise

Request body limits

Endpoint	Limit
`POST /run`	25 MB
`POST /workflows/{id}/validate-input`	25 MB
`POST /workflow-builder/agent/session/from-workflow`, `POST /workflow-builder/agent/session/from-failed-run`	25 MB
`POST /workflows`, `PUT /workflows/{id}`, `POST /workflows/upsert`, `POST /workflows/import`	5 MB
All other endpoints	1 MB

A larger body returns 413 Payload Too Large:

{
  "statusCode": 413,
  "code": "PAYLOAD_TOO_LARGE",
  "message": "Request body is too large",
  "limit_bytes": 26214400,
  "received_bytes": 27262976
}

received_bytes is present when the request sets Content-Length.

Field limits

Field	Limit	Code
Workflow `nodes`	2 MB	`WORKFLOW_NODES_TOO_LARGE`
Workflow `edges`	512 KB	`WORKFLOW_EDGES_TOO_LARGE`
Workflow `input_schema`	256 KB	`INPUT_SCHEMA_TOO_LARGE`
Workflow `output_schema`	128 KB	`OUTPUT_SCHEMA_TOO_LARGE`
Workflow `vault_schema`	32 KB	`VAULT_SCHEMA_TOO_LARGE`
Workflow `name`	256 characters	`WORKFLOW_NAME_TOO_LONG`
Workflow `description`	4,096 characters	`WORKFLOW_DESCRIPTION_TOO_LONG`
Workflow `version_note`	2,048 characters	`VERSION_NOTE_TOO_LONG`
Run `dry_run.add_to_output`	4 KB	`DRY_RUN_OUTPUT_TOO_LARGE`

Byte limits apply to the stored size, which the database may compress. A JSON value can therefore exceed its limit in raw size and still be accepted. A value over its limit returns 400 Bad Request:

{
  "statusCode": 400,
  "code": "WORKFLOW_NODES_TOO_LARGE",
  "message": "nodes exceeds the 2097152-byte limit",
  "field": "nodes",
  "limit_bytes": 2097152
}

Field	Description
`code`	Stable identifier of the limit that was hit
`field`	Request field that exceeded the limit
`limit_bytes` / `limit_chars`	The limit, in bytes or characters
`actual_chars`	Length of the submitted value. Present for `version_note`

A request that also fails other validation returns code: "VALIDATION_FAILED" and lists every error in message.