Skip to content
Cyoda Documentation
Settings

NOT_FOUND — generic resource not found

cyoda-go version 0.7.1

errors.NOT_FOUND

Section titled “errors.NOT_FOUND”

NAME

Section titled “NAME”

NOT_FOUND — the requested resource (key pair, trusted key, or other admin-managed object) does not exist.

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 404 Not Found. Retryable: no.

DESCRIPTION

Section titled “DESCRIPTION”

Returned by administrative endpoints (key pair lifecycle, trusted-key lifecycle) when the supplied identifier does not match any registered resource. The submitted identifier is never echoed in the response body — only a generic descriptor — so attackers cannot use the response as a reflection oracle. The identifier is logged server-side at INFO for operator correlation.

Domain-specific not-found conditions (entity, model, transition, workflow, search-job) have their own dedicated codes — see SEE ALSO.

Not retryable; the resource must be created or registered before the request can succeed.

SEE ALSO

Section titled “SEE ALSO”
  • errors
  • errors.ENTITY_NOT_FOUND
  • errors.MODEL_NOT_FOUND

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 ENTITY_NOT_FOUND — No entity with the given ID exists in the tenant’s data store, or the entity existed at a point-in-time that precedes the requested snapshot. Also returned for audit log lookups when the specified event or message cannot be found.
  • cyoda help errors MODEL_NOT_FOUND — The entity type or model name specified in the request does not exist in the tenant’s model registry. Occurs when creating entities with an unknown type, importing data that references a missing model, or performing model lifecycle transitions on a model ID that does not exist.

Raw formats

Section titled “Raw formats”