Every trap, with the date it was last checked.
Paste an error message to find the trap behind it, or filter by tool.
514 traps
- fg-0300Next.jsVerified Oct 2026'Failed to find Server Action' errors when Next.js runs on more than one container or after a deploy
Error: Failed to find Server Action "7f3a...". This request might be from an older or newer deployment.
verified 2026-10-15 · 0 confirmations
- fg-0299Next.jsVerified Oct 2026Enabling cacheComponents breaks the build on export const dynamic, revalidate, fetchCache or dynamicParams
Route segment config "dynamicParams" is not compatible with `nextConfig.cacheComponents`.
verified 2026-10-15 · 0 confirmations
- fg-0298Next.jsVerified Oct 2026Build fails with 'encountered the unstable value crypto.randomUUID()' after enabling cacheComponents
Route "/account": Next.js encountered the unstable value `crypto.randomUUID()` while prerendering.
verified 2026-10-15 · 0 confirmations
- fg-0297Next.jsVerified Oct 2026Build fails on Next.js 16 because a parallel route slot has no default.js
Missing required default.js file for parallel route at app/@modal
verified 2026-10-15 · 0 confirmations
- fg-0296PrismaVerified Oct 2026Queries hang or fail with 'Unable to start a transaction in the given time' after moving Prisma to driver adapters
Transaction API error: Unable to start a transaction in the given time.
verified 2026-10-15 · 0 confirmations
- fg-0295PrismaVerified Oct 2026Prisma through PgBouncer or the Supabase pooler fails with 'prepared statement "s0" already exists'
prepared statement "s0" already exists
verified 2026-10-15 · 0 confirmations
- fg-0294PrismaVerified Oct 2026Prisma rejects null for a Json field: Type 'null' is not assignable to type 'NullableJsonNullValueInput | InputJsonValue'
Type 'null' is not assignable to type 'NullableJsonNullValueInput | InputJsonValue | undefined'.
verified 2026-10-15 · 0 confirmations
- fg-0293PrismaVerified Oct 2026prisma migrate dev on a managed database fails with 'permission denied to create database'
A migration failed when applied to the shadow database
verified 2026-10-15 · 0 confirmations
- fg-0292PrismaVerified Oct 2026prisma migrate dev in CI or against a shared database detects drift and wants to reset the schema
Drift detected: Your database schema is not in sync with your migration history.
verified 2026-10-15 · 0 confirmations
- fg-0291PrismaVerified Oct 2026prisma generate fails in CI or Docker builds with 'PrismaConfigEnvError: Cannot resolve environment variable: DATABASE_URL'
Error: PrismaConfigEnvError: Cannot resolve environment variable: DATABASE_URL.
verified 2026-10-15 · 0 confirmations
- fg-0290PrismaVerified Oct 2026@prisma/adapter-pg ignores ?schema= in the connection URL and queries the public schema
The table `public.Item` does not exist in the current database.
verified 2026-10-15 · 0 confirmations
- fg-0289PrismaVerified Oct 2026Prisma 7 with @prisma/adapter-pg fails with P1010 or a certificate error on a database that worked with Prisma 6
P1010: User was denied access on the database
verified 2026-10-15 · 0 confirmations
- fg-0288PrismaVerified Oct 2026Prisma 7: 'PrismaClient was instantiated without any options. A driver adapter is required'
PrismaClient was instantiated without any options. A driver adapter is required to connect to your database.
verified 2026-10-15 · 0 confirmations
- fg-0286PrismaVerified Oct 2026Prisma 7 error P1012: The datasource property `url` is no longer supported in schema files
Error code: P1012
verified 2026-10-15 · 0 confirmations
- fg-0285PrismaVerified Oct 2026Next.js dev server runs out of database connections because each hot reload creates a new PrismaClient
FATAL: sorry, too many clients already while running next dev
verified 2026-10-15 · 0 confirmations
- fg-0284PrismaVerified Oct 2026JSON responses with Prisma results throw 'Do not know how to serialize a BigInt' or turn Decimals into strings
TypeError: Do not know how to serialize a BigInt
verified 2026-10-15 · 0 confirmations
- fg-0282PostgreSQLVerified Oct 2026Serverless or hot-reloading apps hit 'sorry, too many clients already' on PostgreSQL
FATAL: sorry, too many clients already
verified 2026-10-15 · 0 confirmations
- fg-0281PostgreSQLVerified Oct 2026psycopg 3 'with connection' block closes the connection that psycopg2 kept open
psycopg.OperationalError: the connection is closed
verified 2026-10-15 · 0 confirmations
- fg-0280PostgreSQLVerified Oct 2026psycopg 3 through PgBouncer fails after a few runs with 'prepared statement "_pg3_0" already exists'
psycopg.errors.DuplicatePreparedStatement: prepared statement "_pg3_0" already exists
verified 2026-10-15 · 0 confirmations
- fg-0279PostgreSQLVerified Oct 2026psycopg 3 raises 'syntax error at or near "$1"' on SET or NOTIFY with parameters that worked in psycopg2
psycopg.errors.SyntaxError: syntax error at or near "$1"
verified 2026-10-15 · 0 confirmations
- fg-0278PostgreSQLVerified Oct 2026postgres:latest container refuses to start with 'database files are incompatible with server'
FATAL: database files are incompatible with server
verified 2026-10-15 · 0 confirmations
- fg-0277PostgreSQLVerified Oct 2026postgres.js through PgBouncer or the Supabase pooler fails with 'prepared statement already exists'
PostgresError: prepared statement "p1" already exists
verified 2026-10-15 · 0 confirmations
- fg-0276PostgreSQLVerified Oct 2026postgres:18 container fails to start or loses data when the volume is mounted at /var/lib/postgresql/data
error mounting "..." to rootfs at "/var/lib/postgresql/data": ... no such file or directory: unknown
verified 2026-10-15 · 0 confirmations
- fg-0275PostgreSQLVerified Oct 2026pg_upgrade to PostgreSQL 18 stops with 'old cluster does not use data checksums but the new one does'
old cluster does not use data checksums but the new one does
verified 2026-10-15 · 0 confirmations