Skip to content
Cyoda Documentation
Settings

POLYMORPHIC_SLOT — payload does not satisfy polymorphic slot constraint

cyoda-go version 0.6.2

errors.POLYMORPHIC_SLOT

Section titled “errors.POLYMORPHIC_SLOT”

NAME

Section titled “NAME”

POLYMORPHIC_SLOT — the entity payload does not satisfy the model’s polymorphic slot definition.

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 400 Bad Request. Retryable: no.

DESCRIPTION

Section titled “DESCRIPTION”

A model can define polymorphic slots — fields whose schema varies based on a discriminator value. This error fires when the payload’s discriminator selects a variant whose schema the provided data fails to match, or when the discriminator value itself is unrecognised.

Not retryable. The model’s polymorphic slot definition determines valid discriminator values and their corresponding schemas.

SEE ALSO

Section titled “SEE ALSO”
  • errors
  • errors.BAD_REQUEST
  • 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 errors BAD_REQUEST — Fired when the server cannot parse or structurally process the incoming request. Common triggers include invalid JSON, missing required fields, unsupported format specifiers, or mutually exclusive parameters being set simultaneously.
  • 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”