TooManyResults

Andromeda answers 403 with the problem type https://uri.etsi.org/ngsi-ld/errors/TooManyResults. The query is well formed and within the complexity limits, but its answer would be more than a cap allows. Andromeda refuses rather than serve a truncated or smaller answer. The specification defines this type and binds it to 403.

When this comes back

Every limit here is Andromeda's own, and the detail names the one you hit.

• A limit above 1,000 on any paged collection, meaning entities, temporal evolutions, subscriptions, context source subscriptions, registrations, @contexts or tenants. The page size is the limit you ask for, so a larger one is refused rather than answered with a smaller page. See Pagination.
• A page of entities, temporal evolutions, subscriptions or registrations that renders to more than request_limits.max_page_body (64 MiB by default). The page is refused whole, naming its size and the ceiling, rather than cut short. Ask for a smaller limit and follow the next page pointer. See Pagination.
• A temporal delete by query matching more instances than extensions.temporal_delete_by_query.max_matches (100,000 by default). Andromeda counts first, and over the limit nothing is removed. See Temporal delete-by-query.
• A grouped aggregation producing more distinct groups than extensions.temporal_aggregation_grouping.max_groups (10,000 by default). See Temporal aggregation grouping.
• A federated temporal query that asks a source what it held before the window opens (timerel=before with lastN=1). That question is bounded like the window query itself, and going over the bound is refused. See Distributed operations.