Skip to content
Cyoda Documentation
Settings

TRANSITION_NOT_FOUND — workflow transition does not exist

cyoda-go version 0.6.2

errors.TRANSITION_NOT_FOUND

Section titled “errors.TRANSITION_NOT_FOUND”

NAME

Section titled “NAME”

TRANSITION_NOT_FOUND — the requested workflow transition is not defined for the entity’s current state.

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 404 Not Found. Retryable: no.

DESCRIPTION

Section titled “DESCRIPTION”

Entity workflow state machines define explicit transitions between states. This error fires when a transition is triggered that does not exist in the model’s workflow definition for the entity’s current state. Also occurs when the transition name is misspelled or when the entity is in a terminal state that allows no further transitions.

Not retryable. The workflow definition and the entity’s current state determine which transition names are valid.

SEE ALSO

Section titled “SEE ALSO”
  • errors
  • errors.WORKFLOW_NOT_FOUND
  • errors.WORKFLOW_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 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 WORKFLOW_FAILED — During an entity create or transition operation the associated workflow processors (pre-processors, post-processors) or guard conditions ran but one of them signalled failure. The failure message from the processor is included in the error detail.

Raw formats

Section titled “Raw formats”