Shared error and limits catalog.

Cross-product guidance for common HTTP statuses, unsupported behavior, limits, and retry choices. Product references remain the source of truth for exact status bodies, route-specific codes, headers, and request shapes.

Common Errors

Shared status guidance across product references
Status	Shared meaning	Typical product codes	Retry guidance
`400`	Request validation failed.	invalid_request, invalid_query, InvalidURI, malformed_json, malformed_request	Fix request shape before retrying.
`401 or 403`	Admission or authorization failed.	AccessDenied, authentication_required, authentication_failed, missing_authorization, invalid_bearer_token	Retry only after fixing credentials, tenant context, or local token values.
`404`	Resource is missing or not visible.	NoSuchBucket, NoSuchKey, stream_not_found, missing_stream, delivery_not_found, not_found	Re-list or re-inspect current state before retrying.
`409`	Request conflicts with current state.	stream_already_exists, lease_expired, lease_not_active, replication_not_configured, ignored_stale	Refresh state or configure the missing runtime binding.
`413 or 422`	Size, batch, retention, or policy limit failed.	EntityTooLarge, invalid_page_size, retention-policy rejection	Reduce size, page, batch, or policy input before retrying.
`429`	Quota, pressure, or concurrency cap is saturated.	quota_exceeded, SlowDown, gateway pressure	Back off and honor Retry-After when present.
`503`	Runtime path is unavailable or not ready.	replication_unavailable, publication failure, readiness blocker, store_unavailable	Check health, readiness, storage, or runtime binding before retrying.

Shared Limit Families

Limit families reused by product references
Limit family	Applies to	Reader guidance
Request shape	Route tokens, query strings, JSON, protobuf, CLI flags, config keys	Match the product reference exactly; do not retry malformed input unchanged.
Payload and batch size	Object bodies, OTLP batches, replay pages, delete bodies, queue claims	Reduce payload, batch, or page size; use product-specific chunking or multipart paths where available.
Auth and tenant context	Local headers, bearer tokens, configured credentials, tenant admission	Treat each product's local credential examples as scoped development values.
Pressure and quota	Concurrent ingress, tenant quotas, gateway budgets, readiness blockers	Back off, reduce concurrency, and inspect health or diagnostics before retrying.
Local or preview boundaries	Local adapters, diagnostic routes, validation commands, fixture-backed contracts	Keep local-only, preview, and verification-required wording in product docs and examples.

Product Notes

ObjectDB

Product-specific

ObjectDB uses S3-shaped error names for the active S3 Core gateway.

Common errors

NotImplemented, AccessDenied, NoSuchBucket, NoSuchKey, BucketAlreadyOwnedByYou, BucketNotEmpty, BadDigest, EntityTooLarge, SlowDown, RequestTimeout, InvalidURI, PreconditionFailed.

Limits

Request target bytes, aggregate header bytes, query parameter count, body chunk buffer, concurrent S3 requests, slow-client timeout, and temporary local adapter caps.

S3 and HTTP reference Configuration reference

Message Broker

Product-specific

Message Broker uses structured JSON errors across stream, record, cursor, queue, replication, audit, metrics, and storage-admin routes.

Common errors

invalid_request, invalid_query, stream_not_found, missing_stream, delivery_not_found, lease_expired, lease_not_active, replication_not_configured, quota_exceeded, replication_unavailable, internal_error.

Limits

Route-family limits include stream and replay paging, payload bytes, queue lease state, tenant quota, replication binding, audit export, metrics exposure, and storage-admin dry-run inputs.

HTTP reference CLI and SDK reference

LogDB

Product-specific

LogDB separates endpoint helper, OTLP HTTP/protobuf, JSON compatibility, optional gRPC, query, configuration, and BYOC handoff errors.

Common errors

unsupported content type, malformed protobuf or JSON, tenant admission failure, gateway pressure, retryable publication failure, invalid query, deadline_exceeded, segment scan or read failure.

Limits

OTLP batch cap, gateway in-flight budgets, tenant admission window, query page size, endpoint recent readback size, S3 query-store selection, WAL mode, and BYOC handoff validation.

OTLP and query reference Configuration and BYOC reference

Concordia

Product-specific

Concordia spans local Cache, TSDB, Gateway, Storage validation, active compatibility, and protocol-registry surfaces.

Common errors

missing_authorization, invalid_bearer_token, malformed_json, not_found, ignored_stale, missing_idempotency_key, conflicting_idempotency_key, readiness blockers, store_unavailable.

Limits

Local bearer-token admission, process-local TSDB storage, Gateway alpha readiness, Storage validation boundaries, active compatibility in-memory state, and future protocol-frame allocations.

Runtime reference

Retry Rules

Fix Client Input

Do not retry unchanged input after validation, authorization, missing-resource, conflict, size, or policy failures.

Back Off Under Pressure

For quota and pressure responses, reduce concurrency and honor Retry-After when the product returns it.

Check Readiness

For unavailable runtime paths, inspect product health, readiness, storage, replication, publication, or Gateway blocker details.

Review Boundary

Product references remain authoritative for exact error bodies and limits. Internal review records track the shared catalog that keeps cross-product language aligned.