Skip to content
Cyoda Documentation
Settings

WORKFLOW_SCHEMA_VERSION_UNSUPPORTED — workflow schema version not accepted

cyoda-go version 0.8.2

errors.WORKFLOW_SCHEMA_VERSION_UNSUPPORTED

Section titled “errors.WORKFLOW_SCHEMA_VERSION_UNSUPPORTED”

NAME

Section titled “NAME”

WORKFLOW_SCHEMA_VERSION_UNSUPPORTED — the workflow definition uses a schema version that this server does not accept.

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 400 Bad Request. Retryable: no.

DESCRIPTION

Section titled “DESCRIPTION”

Every workflow definition must declare a schema version in MAJOR.MINOR format (for example "version": "1.1"). This error is returned when the import request contains a version string that does not match any supported schema version.

Common causes:

  • The "version" field is a bare integer (e.g. "1") instead of MAJOR.MINOR (e.g. "1.1").
  • The "version" field refers to a future or deprecated schema revision not supported by this server build. v0.8.0 retires the 1.0 minor used by release/v0.7.x; payloads stamped "1.0" are rejected and must be regenerated against 1.1.
  • The "version" field is missing from one or more workflow objects in the import payload.

Correct the "version" field in every workflow object within the workflows array to use "1.1" (or the current supported version), then resubmit the import request.

Discover the current supported set via cyoda help workflows schema-version versions or GET /help/workflows/schema-version/versions.

SEE ALSO

Section titled “SEE ALSO”
  • errors
  • workflows.schema-version
  • errors.WORKFLOW_NOT_FOUND
  • errors.VALIDATION_FAILED

See also

Section titled “See also”
  • cyoda help errors — Every error response from the Cyoda REST API carries a structured errorCode in the properties object. Multiple codes may share the same HTTP status. Programmatic handling keys on errorCode, not HTTP status.
  • cyoda help workflows schema-version — workflows schema-version — semver MAJOR.MINOR contract identifying the workflow-import DTO shape that a workflow definition was authored against.
  • cyoda help errors WORKFLOW_NOT_FOUND — Entity models reference a workflow by name to govern state transitions. This error is returned when the named workflow cannot be found in the tenant’s workflow registry, during entity type registration or when a model references a workflow that was deleted.
  • cyoda help errors VALIDATION_FAILED — Unlike BAD_REQUEST (which covers parse failures), this error is returned when the payload is parseable but violates the registered model schema — for example, a required field is missing, a value is out of the allowed range, or a workflow guard condition is not satisfied. The error detail includes the specific validation failure.

Raw formats

Section titled “Raw formats”