Skip to content
Cyoda Documentation
Settings

MODEL_HAS_ENTITIES — operation blocked because entities of this model exist

cyoda-go version 0.7.1

errors.MODEL_HAS_ENTITIES

Section titled “errors.MODEL_HAS_ENTITIES”

NAME

Section titled “NAME”

MODEL_HAS_ENTITIES — an unlock or delete request was rejected because at least one entity of the target model still exists.

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 409 Conflict. Retryable: no.

DESCRIPTION

Section titled “DESCRIPTION”

Both POST /model/{name}/{version}/unlock and DELETE /model/{name}/{version} require zero entities of the target model. The cardinality check guards against silent loss of data and against schema drift on a model whose lifecycle is presumed frozen.

The entityCount property in the problem-detail body reports how many entities currently exist for the model on the responding tenant.

Not retryable in the protocol sense. The caller must remove the offending entities (e.g. via condition-delete on the entity surface) and re-issue the lifecycle request.

SEE ALSO

Section titled “SEE ALSO”
  • errors
  • errors.MODEL_ALREADY_LOCKED
  • errors.MODEL_ALREADY_UNLOCKED
  • errors.CONFLICT

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_ALREADY_LOCKED — Returned by any admin operation that requires the model be in the UNLOCKED state, including:
  • cyoda help errors MODEL_ALREADY_UNLOCKED — Returned when POST /model/{name}/{version}/unlock is issued against a model whose current state is UNLOCKED. Distinct from MODEL_NOT_LOCKED, which is reserved for the entity-write-without-lock path on the entity service: this code is the symmetric counterpart of MODEL_ALREADY_LOCKED for the admin lifecycle.
  • cyoda help errors CONFLICT — The server detected that the entity was modified by another writer between the time it was read and the time the current write was committed. Normal outcome under concurrent load.

Raw formats

Section titled “Raw formats”