Drizzle "Failed query" error: find the real cause

Failed query: is Drizzle telling you which SQL it sent, not what went wrong. Since drizzle-orm 0.44.0, every database error is wrapped in a DrizzleQueryError whose message is only the query and its parameters. The reason, the error from Postgres itself, is attached as cause. On 0.43.1 the same insert threw the Postgres error directly.

I reproduced five common causes on drizzle-orm 0.45.4. Every one produced the same kind of message, so the SQL alone doesn’t tell them apart.

Read the cause

try {
  await db.insert(users).values({ email, name });
} catch (e) {
  console.log(e.cause?.message, e.cause?.code);
}

These are the five, with what the wrapper said and what e.cause said:

The params line can hint at it (an empty value after the last comma, 999 for an author ID), but only the cause says it outright.

Why you only see “Failed query”

The cause isn’t hidden from Node: console.error(e) prints it, further down after the stack trace, as cause: error: relation "nope" does not exist. It disappears wherever only the message is used: e.message, String(e), an error toast, a JSON response like { error: e.message }, or an error tracker that groups by message. All of those show the SQL and nothing else, which is why the same “Failed query” seems to have no explanation.

e.code === '23505' stopped working in 0.44

This is the breaking part of the change. A common way to turn a duplicate email into a friendly “that email is taken” message is to check the Postgres error code. I ran the same duplicate insert on three versions:

So after upgrading, a check on e.code is silently never true: no error, just the friendly message never shows, and the raw failure reaches the user instead.

import { DrizzleQueryError } from 'drizzle-orm/errors';

const pgError = (e: unknown) => (e instanceof DrizzleQueryError ? e.cause : e) as { code?: string } | undefined;

try {
  await db.insert(users).values({ email, name });
} catch (e) {
  if (pgError(e)?.code === '23505') return { error: 'That email is already registered.' };
  throw e;
}

The cause with node-postgres and postgres.js

Against a real Postgres 17 server, both popular drivers gave the same wrapper and the same e.cause.code, but the error inside differs, and one field name differs:

detail is the most useful line for a duplicate: it names the column and the value. If you tell users which field is taken based on the constraint name, read the right property for your driver: constraint was undefined on postgres.js, and constraint_name was undefined on pg.

“applying migrations…” then Failed query: CREATE TABLE

The migration version of this error usually means the table already exists, created by drizzle-kit push or by hand, outside the migrations Drizzle keeps track of. I created users directly, then ran the generated migration through Drizzle’s migrate():

DrizzleQueryError: Failed query:
CREATE TABLE "users" (
	"id" serial PRIMARY KEY NOT NULL,
	"email" text NOT NULL,
	...
cause: relation "users" already exists (code 42P07)

With the PGlite driver, drizzle-kit migrate itself printed nothing but its spinner and exited with code 1. Only running the migration from code showed the cause. If your migrate step fails silently, run it once through migrate() in a small script to see the error.

I didn’t test moving an existing pushed database onto migrations. In development, recreating the database and running the migrations from the start is the simple way out.

What didn’t work

How this was tested

drizzle-orm 0.45.4 (the latest), 0.44.0 and 0.43.1 with the PGlite 0.5.8 driver (Postgres compiled to WebAssembly), and 0.45.4 with node-postgres 8 and postgres.js 3 against a Postgres 17 server in Docker. Each case was a fresh in-memory database with a users table (unique email, required name) and a posts table with a foreign key to it. Migrations were generated with drizzle-kit 0.31.11 and applied with drizzle-kit migrate and with migrate() from drizzle-orm/pglite/migrator. Node 24.14.0 on Windows 11, October 10, 2026.

The code is public, so you can run it yourself: drizzle-failed-query in nk-repro.