> For the complete documentation index, see [llms.txt](https://learn.mechanic.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.mechanic.dev/faq/query-param-length-is-too-long.md).

# I'm getting a "query param length is too long" error when using GraphQL.

This error is about the length of the GraphQL query as a whole (which Shopify limits to 50,000 characters in total), and *not* about specific strings within the query. (Using an example from the Mechanic task library, [this scenario](https://github.com/lightward/mechanic-tasks/blob/fc08062fb1b861c95f4244c1c12f231646770700/docs/sync-inventory-for-shared-skus/script.liquid#L17-L44) could return this error if the list of list of SKUs is extremely long.)

To work around this error, refactor your query so that any long string values are provided using GraphQL variables, instead of provided inline.

{% hint style="info" %}
Learn about this technique using the [Shopify action](/core/actions/shopify.md#graphql-with-variables), or with the [shopify Liquid filter](/platform/liquid/filters.md#shopify).
{% endhint %}

If your query *isn't* using any particularly large string values, you may need to split your query into several pieces instead.


---

# 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://learn.mechanic.dev/faq/query-param-length-is-too-long.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.