Skip to content
Settings

INVALID_LIMIT — grouped-stats limit is non-positive or above the ceiling

cyoda-go version 0.8.4

INVALID_LIMIT — the grouped-statistics request’s limit is not a positive integer at or below CYODA_STATS_GROUP_MAX.

HTTP: 400 Bad Request. Retryable: no.

Raised by POST /api/entity/stats/{entityName}/{modelVersion}/query. limit is optional; when present it is a top-N cap on the buckets returned, and it must be greater than zero and no greater than the server’s CYODA_STATS_GROUP_MAX (default 10000). A value outside that range is rejected up front rather than clamped, so the response never silently covers a smaller set than the one asked for. The message carries the configured maximum.

Omit limit for all buckets, up to the cardinality ceiling. If the ceiling itself is too low for the deployment, an operator raises CYODA_STATS_GROUP_MAX.

  • errors
  • crud
  • config
  • errors.GROUP_CARDINALITY_EXCEEDED
  • 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 crud — Entities are instances of models. Each entity has a UUID, a model reference (entityName, modelVersion), and a lifecycle state managed by the workflow engine. Creating an entity requires the referenced model to be in LOCKED state. All write operations run within a Cyoda transaction and return a transactionId alongside the affected entity IDs.
  • cyoda help config — Environment variables beat default values. The _FILE suffix variant takes precedence over the plain variable when both are set — for example, CYODA_POSTGRES_URL_FILE=/etc/secrets/db-url wins over CYODA_POSTGRES_URL. There are no command-line flags for configuration values; env vars are the sole configuration surface.
  • cyoda help errors GROUP_CARDINALITY_EXCEEDED — Raised by POST /api/entity/stats/{entityName}/{modelVersion}/query. CYODA_STATS_GROUP_MAX (default 10000) bounds the number of distinct buckets the endpoint will build. The bound is enforced on both execution paths — the backend’s native GROUP BY pushdown and the in-process streaming tally — so the same query is rejected identically on every storage backend.