# DISPATCH_TIMEOUT — dispatch to compute member timed out

A workflow processor or criteria evaluation was dispatched to a compute member but the response did not arrive within the dispatch timeout window. The und…

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

# errors.DISPATCH_TIMEOUT

## NAME

DISPATCH_TIMEOUT — the dispatcher waited longer than the configured timeout for a compute member to accept and complete a task.

## SYNOPSIS

HTTP: `503` `Service Unavailable`.

## DESCRIPTION

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.

Retryable. Completion on the remote node is not guaranteed; retries must be idempotent or carry an idempotency key.

If timeouts recur, check compute member load and network latency. The relevant configuration variables are `CYODA_DISPATCH_WAIT_TIMEOUT` (how long the dispatcher polls gossip for a compute member with matching tags; default `5s`) and `CYODA_DISPATCH_FORWARD_TIMEOUT` (HTTP timeout for the cross-node forwarding call; default `30s`).

## SEE ALSO

- errors
- errors.DISPATCH_FORWARD_FAILED
- errors.NO_COMPUTE_MEMBER_FOR_TAG

## 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 DISPATCH_FORWARD_FAILED`](/help/errors/dispatch_forward_failed/) — 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.
- [`cyoda help errors NO_COMPUTE_MEMBER_FOR_TAG`](/help/errors/no_compute_member_for_tag/) — 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.

## Raw formats

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