Skip to content
Cyoda Documentation
Settings

SEARCH_RESULT_LIMIT — search result set exceeds the allowed limit

cyoda-go version 0.8.3

errors.SEARCH_RESULT_LIMIT

Section titled “errors.SEARCH_RESULT_LIMIT”

NAME

Section titled “NAME”

SEARCH_RESULT_LIMIT — the search query’s matched entity count exceeded the requested limit, a cap on the matched set, not a page size.

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 400 Bad Request. Retryable: no.

DESCRIPTION

Section titled “DESCRIPTION”

Direct (synchronous) search is bounded-or-fail: limit caps the matched result set rather than paging it. When more entities match than the limit allows, the request is rejected — it never returns a truncated prefix, because a partial result would be indistinguishable from a complete one.

Not retryable with the same parameters. Narrow the condition, raise limit (up to the documented maximum), or use async search, which snapshots the full result set and pages over it.

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 SCAN_BUDGET_EXHAUSTED — Some conditions are not indexable — for example a regex or a wildcard path match — so the backend must scan candidate rows and post-filter them in the engine instead of pushing the predicate to storage. When the number of rows scanned this way exceeds the configured scan-budget limit, the request fails fast instead of running unbounded.
  • 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”