# CLUSTER_NODE_NOT_REGISTERED — target node is not in the cluster registry

The request was routed to or requires a specific cluster node that is not present in the registry. Occurs during startup, rolling restarts, or after a nod…

<em>cyoda-go version <a href="https://github.com/Cyoda-platform/cyoda-go/releases/tag/v0.6.2">0.6.2</a></em>

# errors.CLUSTER_NODE_NOT_REGISTERED

## NAME

CLUSTER_NODE_NOT_REGISTERED — the target cluster node has not registered itself with the gossip registry.

## SYNOPSIS

HTTP: `503` `Service Unavailable`. Retryable: `yes`.

## DESCRIPTION

The request was routed to or requires a specific cluster node that is not present in the registry. Occurs during startup, rolling restarts, or after a node failure before the gossip layer has converged.

Retryable. Gossip convergence determines when the node becomes available. Persistence beyond the expected convergence window indicates a node health or cluster membership issue.

## SEE ALSO

- errors
- errors.COMPUTE_MEMBER_DISCONNECTED

## See also

- [`cyoda help errors`](/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`](/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.

## Raw formats

- [`/help/errors/cluster_node_not_registered.json`](/help/errors/cluster_node_not_registered.json) — full descriptor (matches `GET /help/{topic}` envelope)
- [`/help/errors/cluster_node_not_registered.md`](/help/errors/cluster_node_not_registered.md) — body only