> For the complete documentation index, see [llms.txt](https://docs.trustlesswork.com/trustless-work/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trustlesswork.com/trustless-work/v2-en/api-rest/errors/generic-http/query-too-complex.md).

# QUERY\_TOO\_COMPLEX

The GraphQL query exceeds the complexity budget.

`400 Bad Request` · GraphQL

Unlike the REST codes, this one travels in the GraphQL error envelope: `errors[].extensions.code`.

### Example

```json
{
  "errors": [
    {
      "message": "Query complexity 200000 exceeds the maximum of 5000. Reduce page sizes, nesting or aliased list fields.",
      "extensions": { "code": "QUERY_TOO_COMPLEX" }
    }
  ]
}
```

### When it happens

The document's estimated cost — page sizes multiplied through nested and aliased list fields, computed with the request's real variable values — exceeds the server's complexity budget. The request is rejected before any resolver runs.

### How to fix it

Ask for less per request: smaller `limit`s, fewer nesting levels, fewer aliased list fields. Page through results with cursors instead of widening one query.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.trustlesswork.com/trustless-work/v2-en/api-rest/errors/generic-http/query-too-complex.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.