Skip to content
Cyoda Documentation
Settings

SEARCH_RESULT_LIMIT — search result set exceeds the allowed limit

cyoda-go version 0.6.2

errors.SEARCH_RESULT_LIMIT

Section titled “errors.SEARCH_RESULT_LIMIT”

NAME

Section titled “NAME”

SEARCH_RESULT_LIMIT — the search query matched more results than the server-enforced maximum page or result set size.

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 400 Bad Request. Retryable: no.

DESCRIPTION

Section titled “DESCRIPTION”

The server imposes an upper bound on the number of results returned per page and per job to protect cluster resources. Returned when the request exceeds this limit — either by requesting too large a page size or by the matched result count exceeding the cap.

Not retryable with the same parameters. A smaller pageSize or more selective filter conditions reduce the result set below the cap.

SEE ALSO

Section titled “SEE ALSO”
  • errors
  • errors.SEARCH_JOB_NOT_FOUND
  • errors.SEARCH_SHARD_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 SEARCH_JOB_NOT_FOUND — Polling a search job by ID returns this error when the job ID is unknown or belongs to a different tenant. Jobs are tenant-scoped; a valid job ID from one tenant is not visible to another.
  • cyoda 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

Section titled “Raw formats”