Skip to content
Cyoda Documentation
Settings

SEARCH_JOB_ALREADY_TERMINAL — search job has already completed or failed

cyoda-go version 0.6.2

errors.SEARCH_JOB_ALREADY_TERMINAL

Section titled “errors.SEARCH_JOB_ALREADY_TERMINAL”

NAME

Section titled “NAME”

SEARCH_JOB_ALREADY_TERMINAL — an operation was attempted on a search job that has already reached a terminal state (completed, failed, or cancelled).

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 409 Conflict. Retryable: no.

DESCRIPTION

Section titled “DESCRIPTION”

Search jobs are long-running asynchronous operations. Once a job reaches a terminal state it cannot be cancelled, resumed, or otherwise modified. This error is returned when such an operation is attempted on a finished job.

Not retryable on the same job. Results from a successfully completed job remain available for retrieval.

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”