Error map

200 API returns 200 OK with an error in the body (errors hidden from clients and monitors)

HTTP · layer 2, Network

Open the full error page →

Centre: this error. First ring: errors it is linked with (7). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.

200 — API returns 200 OK with an error in the body (errors hidden from clients and monitors) (HTTP)200422 — HTTP 422 Unprocessable Content (HTTP)422200 — HTTP 200 OK (but something is still wrong) (HTTP)200203 — HTTP 203 Non-Authoritative Information (HTTP)203201 — HTTP 201 Created (HTTP)201102 — HTTP 102 Processing (HTTP)102202 — HTTP 202 Accepted (HTTP)202404 — Soft 404: page returns 200 for missing content (HTTP)404400 — HTTP 400 Bad Request (HTTP)400415 — HTTP 415 Unsupported Media Type (HTTP)415409 — HTTP 409 Conflict (HTTP)409404 — HTTP 404 Not Found (HTTP)404SyntaxError: JSON — SyntaxError: Unexpected token < in JSON at position 0 (JavaScript)SyntaxError: JSONGRAPHQL_VALIDATION_FAILED — GraphQL: Cannot query field "x" on type "Y" (API)GRAPHQL_VALIDATION_…407 — HTTP 407 Proxy Authentication Required (HTTP)407304 — HTTP 304 Not Modified (HTTP)304417 — HTTP 417 Expectation Failed (HTTP)417506 — HTTP 506 Variant Also Negotiates (HTTP)506204 — HTTP 204 No Content (HTTP)204205 — HTTP 205 Reset Content (HTTP)205507 — HTTP 507 Insufficient Storage (HTTP)507100 — HTTP 100 Continue (HTTP)100103 — HTTP 103 Early Hints (HTTP)103UnhandledPromiseRejection — Node.js: [UnhandledPromiseRejection] — This error originated either by throwing inside of an async function without a catch block (Node.js)UnhandledPromiseRej…await outside async — SyntaxError: await is only valid in async functions and the top level bodies of modules (JavaScript)await outside asyncAbortError — AbortError: The user aborted a request. / signal is aborted without reason (JavaScript)AbortError410 — HTTP 410 Gone (HTTP)410301 — HTTP 301 Moved Permanently (HTTP)301308 — HTTP 308 Permanent Redirect (HTTP)308

Directly related (7)

Two steps away (21)

400HTTP

HTTP 400 Bad Request

The server could not understand the request because its syntax, headers or body are malformed or invalid.

415HTTP

HTTP 415 Unsupported Media Type

The server refuses the request because the body’s Content-Type isn’t one it accepts.

409HTTP

HTTP 409 Conflict

The request conflicts with the current state of the resource — e.g. a duplicate or an edit based on an outdated version.

404HTTP

HTTP 404 Not Found

The server can’t find anything at the requested URL.

SyntaxError: JSONJavaScript

SyntaxError: Unexpected token < in JSON at position 0

`JSON.parse()` / `response.json()` received something that isn’t JSON — very often an HTML error page.

GRAPHQL_VALIDATION_FAILEDAPI

GraphQL: Cannot query field "x" on type "Y"

The query asks for a field that doesn’t exist in the server’s schema (or isn’t available on that type).

407HTTP

HTTP 407 Proxy Authentication Required

A proxy between you and the server requires credentials before it will forward your request.

304HTTP

HTTP 304 Not Modified

The cached copy is still valid, so the server sends no body and the client reuses its cache.

417HTTP

HTTP 417 Expectation Failed

The server or a proxy can’t meet the Expect header in the request — almost always Expect: 100-continue.

506HTTP

HTTP 506 Variant Also Negotiates

The server's content-negotiation setup is circular, so it can't pick a representation.

204HTTP

HTTP 204 No Content

The request succeeded and the server intentionally sent no response body.

205HTTP

HTTP 205 Reset Content

The request succeeded and the client should reset the form or view that sent it.

507HTTP

HTTP 507 Insufficient Storage

The server can’t store what’s needed to complete the request — the disk, quota or mailbox is full.

100HTTP

HTTP 100 Continue

An interim response telling the client to go ahead and send the request body — normal when the client sent Expect: 100-continue.

103HTTP

HTTP 103 Early Hints

An interim response that sends Link headers early so the browser can preload CSS, fonts or scripts while the server is still buil…

UnhandledPromiseRejectionNode.js

Node.js: [UnhandledPromiseRejection] — This error originated either by throwing inside of an async function without a catch block

A promise rejected and nothing handled it; since Node 15 this crashes the process.

await outside asyncJavaScript

SyntaxError: await is only valid in async functions and the top level bodies of modules

await was used inside a function that isn’t async (or in a classic, non-module script).

AbortErrorJavaScript

AbortError: The user aborted a request. / signal is aborted without reason

A fetch was cancelled through an AbortController (or the browser cancelled it).

410HTTP

HTTP 410 Gone

The resource used to exist but was intentionally and permanently removed, with no forwarding address.

301HTTP

HTTP 301 Moved Permanently

The resource has a new permanent URL; clients and search engines should use the address in the Location header from now on.

308HTTP

HTTP 308 Permanent Redirect

A permanent redirect that, unlike 301, guarantees the method and body are kept.