# SEARCH_TIMEOUT — search timeout expired before results collected

Fires when the client-supplied `timeoutMillis` elapses before the search result set was fully collected. No partial results are returned.

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

# errors.SEARCH_TIMEOUT

## NAME

SEARCH_TIMEOUT — the client-supplied `timeoutMillis` expired before the search result set was collected.

## SYNOPSIS

HTTP: `408` `Request Timeout`. Retryable: `yes`.

## DESCRIPTION

Fires when the client-supplied `timeoutMillis` elapses before the search result set was fully collected. No partial results are returned.

## SEE ALSO

- errors
- errors.SEARCH_SHARD_TIMEOUT

## 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 SEARCH_SHARD_TIMEOUT`](/help/errors/search_shard_timeout/) — Distributed search fans out to multiple shards in parallel. If any shard does not return results before the search timeout expires, the job is marked failed and this error is returned. Occurs under high load, during partial cluster degradation, or with expensive queries.

## Raw formats

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