Skip to content

docs: add guide on graphql-http errors #2006

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 13 commits into from
Jun 19, 2025
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update src/pages/learn/debug-errors.mdx
Co-authored-by: Benjie <[email protected]>
  • Loading branch information
sarahxsanders and benjie authored Jun 9, 2025
commit 26f08b76aef67e3e9293b895c89e004ee7226b0f
6 changes: 5 additions & 1 deletion src/pages/learn/debug-errors.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -118,7 +118,11 @@ The HTTP layer succeeded, but the GraphQL request produced errors.

### How to debug

Check the `errors` array in the response body. A typical response looks like:
Check the `errors` array in the response body.

If the response includes a `data` property then your query document is likely valid and you most likely hit a runtime exception - perhaps something went wrong on the server, you supplied invalid data, you're not allowed to do that, or some other runtime exception occurred.

If the response does not include a `data` property it's likely there was a mistake in your request - an invalid GraphQL document or bad values for variables. A typical validation error response looks like:

```json
{
Expand Down