Skip to content
Cyoda Documentation
Settings

ENTITY_NOT_FOUND — entity does not exist

cyoda-go version 0.6.2

errors.ENTITY_NOT_FOUND

Section titled “errors.ENTITY_NOT_FOUND”

NAME

Section titled “NAME”

ENTITY_NOT_FOUND — the requested entity does not exist or is not accessible to the caller.

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 404 Not Found. Retryable: no.

DESCRIPTION

Section titled “DESCRIPTION”

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.

Not retryable. Point-in-time lookups require a timestamp within the entity’s history.

SEE ALSO

Section titled “SEE ALSO”
  • errors
  • 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 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”