Skip to content
Cyoda Documentation
Settings

NO_COMPUTE_MEMBER_FOR_TAG — no compute member registered for the required tag

cyoda-go version 0.7.1

errors.NO_COMPUTE_MEMBER_FOR_TAG

Section titled “errors.NO_COMPUTE_MEMBER_FOR_TAG”

NAME

Section titled “NAME”

NO_COMPUTE_MEMBER_FOR_TAG — the dispatcher found no live cluster node advertising the compute tag required by the workflow or processor.

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 503 Service Unavailable. Retryable: yes.

DESCRIPTION

Section titled “DESCRIPTION”

Workflow processors are dispatched to nodes that advertise matching compute tags. When no node with the required tag is alive in the cluster within the configured wait timeout (CYODA_DISPATCH_WAIT_TIMEOUT), the operation is rejected with this error.

Retryable after compute capacity is restored. At least one live node advertising the required tag is required for dispatch to succeed.

SEE ALSO

Section titled “SEE ALSO”
  • errors
  • errors.COMPUTE_MEMBER_DISCONNECTED
  • errors.DISPATCH_TIMEOUT

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 COMPUTE_MEMBER_DISCONNECTED — The compute member responsible for executing a processor or workflow step disconnected before completing the operation. The task may or may not have been executed.
  • cyoda help errors DISPATCH_TIMEOUT — A workflow processor or criteria evaluation was dispatched to a compute member but the response did not arrive within the dispatch timeout window. The underlying task may or may not have completed on the remote node.

Raw formats

Section titled “Raw formats”