Skip to content
Cyoda Documentation
Settings

MODEL_NOT_LOCKED — model must be locked before writing entities

cyoda-go version 0.8.3

errors.MODEL_NOT_LOCKED

Section titled “errors.MODEL_NOT_LOCKED”

NAME

Section titled “NAME”

MODEL_NOT_LOCKED — the entity model exists but is not in a locked state, which is required before entities of that type can be created or updated.

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 409 Conflict. Retryable: no.

DESCRIPTION

Section titled “DESCRIPTION”

Entity creation and bulk write operations require the model to be in the LOCKED lifecycle state. Models in DRAFT or unlocked-for-editing state reject writes to prevent schema changes from affecting in-flight data.

Not retryable. Entity writes require the model to be in LOCKED state.

SEE ALSO

Section titled “SEE ALSO”
  • errors
  • errors.MODEL_NOT_FOUND
  • 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_NOT_FOUND — The entity type or model name specified in the request does not exist in the tenant’s model registry. Occurs on write paths (creating entities with an unknown type, importing data that references a missing model, performing model lifecycle transitions on a model ID that does not exist) and on read paths (list, stats, grouped-stats, and search operations that reference an unregistered model).
  • 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”