Errors and insights
Errors
Section titled “Errors”A red dot marks a row whose response has errors and no data, or an HTTP error. An amber dot marks errors with partial data. Point at the dot to read the first error, its code first (FORBIDDEN: Not allowed…).
Above the response, each GraphQL error gets a row:
- its code (
extensions.code, or what other servers use instead) and its full message; - where: the path, written as in code (
viewer.orders[1]), which opens that node in the response, and the line and column in the query; - what the code usually means, for common codes such as
UNAUTHENTICATED,FORBIDDEN,BAD_USER_INPUTandGRAPHQL_VALIDATION_FAILED; - Details, folded: the rest of
extensions(a request id, for example) and the server’s stack trace, one frame per line.


The first five errors show; Show more lists the rest. Fold the list to its first message with the arrow, and Copy errors copies them as JSON. The nodes errors point at are tinted in the response tree.
Failed requests
Section titled “Failed requests”A request that failed over HTTP names its status above the response (401 Unauthorized, 504 Gateway Timeout…) with what it usually means and where to look. One that got no response at all shows failed in the Status column, with the likely causes: the network, DNS or TLS, CORS or a blocking extension, or the page cancelling it. When a server or a proxy answers with an HTML error page instead of JSON, Wireglass says so and gives the page’s title.


Deprecated fields
Section titled “Deprecated fields”Operations that use something their endpoint’s schema deprecates are flagged DEPRECATED in the list: a field, a query, mutation or subscription, an argument, an input field or an enum value, whether it is written in the query or passed in the variables. Point at the flag to read what is deprecated and why. Request lists each one with the schema’s reason and where it is used: a line and column in the query, or a path in the variables such as $input.giftNote.


The check uses a schema Wireglass already has for the endpoint: one loaded in the client, which is kept. When there is none, Request says the operation wasn’t checked and offers Load schema, which sends an introspection query to that endpoint with the request’s own headers. Nothing is sent until you click it.
Insights
Section titled “Insights”Each row shows a waterfall bar, its size and its duration. A ⚑ flags:
- a duplicate call: same operation and variables within 500 ms,
- a possible N+1: more than 5 calls of one operation with different variables within 1 s,
- a large response: over 1 MB.
These are hints and may be intentional. Thresholds are in Settings under Traffic.
The Timing tab
Section titled “The Timing tab”Shows the HAR phases, the insights with an explanation, and the resolver tree and cost when the response has extensions.tracing or extensions.cost.
Filter by insight
Section titled “Filter by insight”Type these in the Traffic filter box:
| Filter | Shows |
|---|---|
has:insight |
Rows with a flag |
slow:>500ms |
Operations slower than 500 ms |
size:>1mb |
Responses over 1 MB |
has:mocked |
Rows answered by a mock |
has:deprecated |
Operations that use something the schema deprecates |
© 2026 Melliforge. All rights reserved.