Skip to content
Cyoda Documentation
Settings

DISPATCH_FORWARD_FAILED — inter-node dispatch forwarding error

cyoda-go version 0.8.4

errors.DISPATCH_FORWARD_FAILED

Section titled “errors.DISPATCH_FORWARD_FAILED”

NAME

Section titled “NAME”

DISPATCH_FORWARD_FAILED — forwarding a processor or criteria dispatch request to a peer node failed.

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 503 Service Unavailable. Retryable: yes.

DESCRIPTION

Section titled “DESCRIPTION”

The cluster dispatcher attempted to forward a processor invocation or criteria evaluation to a peer node but the HTTP call to that peer failed (network error, peer crash, or connection refused). The operation has not been executed on the target node.

Retryable. Persistent failures indicate inter-node network or peer node health issues.

SEE ALSO

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

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 DISPATCH_TIMEOUT — A workflow processor, criteria evaluation, or function callout was dispatched to a compute member but the response did not arrive within the callout’s own responseTimeoutMs (a field on the processor, criteria, or function config; default 30000 ms) — not any cluster forwarding timeout.
  • 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.

Raw formats

Section titled “Raw formats”