Skip to content
Cyoda Documentation
Settings

WORKFLOW_FAILED — workflow processor returned an error

cyoda-go version 0.6.2

errors.WORKFLOW_FAILED

Section titled “errors.WORKFLOW_FAILED”

NAME

Section titled “NAME”

WORKFLOW_FAILED — a workflow processor or guard condition returned a failure during entity state transition.

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 400 Bad Request. Retryable: no.

DESCRIPTION

Section titled “DESCRIPTION”

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.

Not retryable unless the underlying condition has changed. The failure originates from application logic in the processor; the data, the processor implementation, or the workflow configuration determines the outcome.

SEE ALSO

Section titled “SEE ALSO”
  • errors
  • errors.WORKFLOW_NOT_FOUND
  • errors.TRANSITION_NOT_FOUND

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 TRANSITION_NOT_FOUND — 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.

Raw formats

Section titled “Raw formats”