File an issue

It goes to nightswatchhq/graph-support, community triage run by The Night’s Watch. You get a root cause, a workaround, or the name of the party who can actually fix it, and the thread stays public so the next person finds it. You can file it here without a GitHub account, or open it on GitHub under your own name, which is the better of the two if you have one.

Do not paste an API key, a deploy key, an operator key, a mnemonic, a keystore or the contents of an .env. A gateway query URL contains an API key: redact it as gateway.thegraph.com/api/<KEY>/….

If you have already posted a key somewhere, rotate it rather than editing the message. Editing does not remove it from the history.

What are you seeing? Paste the literal error if you have one.

This becomes the title, and it is the whole reason anyone finds the thread later.

Reading the issue forms…

A query fails or returns wrong dataA query against a subgraph errors, returns nothing, or returns data you know is wrong or stale.A subgraph will not deploy, sync, or has failedDeployment errors, a subgraph stuck syncing, stuck at 99%, or a failed deployment.An indexer or operator problemFor people running indexers. Chain clients, RPC, snapshots, PoI divergence, allocations, Horizon, staking.The documentation is wrong or unclearSomething in the official docs is incorrect, ambiguous, or led you into a mistake.A questionNot obviously broken, you just want to know how something works or what the right approach is.A symptom the diagnostic index does not coverSomething broke in a way the Academy’s symptom index does not carry, and the next person should not have to work it out again.None of these. Open a blank issue on GitHub.