All Errors

Supabase responds with "user_not_found: User could not be found" when the identifier you supplied (email, phone, or OAuth provider) does not match any row inside auth.users. The fix is usually to confirm the user exists in the right project, create or restore the missing account, and call the correct sign-in flow so Supabase is looking for the provider you expect.

Every MongoDB write concern is guarded by a timeout. When a write needs acknowledgements from more than the primary, the driver waits for those replicas but eventually raises "WriteConcernError: waiting for replication timed out" if the replicas cannot confirm the write before the configured wtimeout expires.

MySQL ERROR 1021 occurs when the server runs out of disk space while writing data or temporary files. The server will pause operations and wait for space to become available. Fix it by freeing disk space, managing binary logs, redirecting the temp directory, or expanding storage.

PostgreSQL throws 2200M (invalid_xml_document) when libxml2 rejects the payload passed to XMLPARSE, XMLTABLE, XML functions, or an xml column insert because the text is not a well-formed XML document. The parser wants a single root node and complete tag structure, so missing roots, stray text nodes, or bad syntax cause the query to fail before the server ever stores or evaluates the value.

This error occurs when the request payload to a Firebase Callable Function is incorrectly formatted. The issue typically stems from extra fields in the request body, missing the required "data" field, or sending non-JSON-serializable data.

This error occurs when better-sqlite3 tries to execute a query while the database connection is already processing another query. It commonly happens when attempting to run an UPDATE or DELETE while iterating through a SELECT result set, or when trying to close the database while a query is still running.

MySQL Error 1203 occurs when a user account exceeds its max_user_connections limit. Fix it by increasing the connection limit, optimizing your application code, or closing idle connections.

This error occurs when you submit a DynamoDB transaction (TransactWriteItems or ExecuteTransaction) using a client request token that is already being used by an ongoing transaction. It indicates a duplicate transaction attempt within the 10-minute idempotency window.

This error occurs when using strict mode in SQL/JSON path expressions to access a non-existent JSON object member or array element. Switch to lax mode or add error handling clauses to suppress the error.

The "phone_provider_disabled: Phone signups are disabled" error occurs when Supabase Auth attempts phone-based authentication but phone signups are not enabled in the project settings. This prevents users from signing up or logging in with phone numbers until phone authentication is properly configured and enabled.

The Prisma P2002 error occurs when you attempt to insert or update a record with a value that violates a unique constraint in your database. This happens when trying to create a duplicate entry for a field marked as @unique, such as an email address that already exists. The fix typically involves checking for existing records before insertion or using upsert operations.

The PostgreSQL error "2D000: invalid_transaction_termination" occurs when a transaction is terminated incorrectly, such as attempting to COMMIT or ROLLBACK at an invalid point in transaction flow. This typically happens when transaction control statements are used improperly within stored procedures, functions, or application code.

PostgreSQL throws the duplicate column error (42701) when you attempt to add a column that already exists or specify the same column name multiple times. Fix it by checking existing columns, using aliases in joins, or leveraging IF NOT EXISTS clauses in migrations.

This PostgreSQL error occurs when invalid arguments are passed to the width_bucket() function, which is used for histogram calculations. The function requires numeric arguments with proper bounds and bucket counts that follow mathematical constraints.

This error occurs when your Docker client uses a newer API version than the daemon it is talking to can support. The fix is to lower the client's API version with DOCKER_API_VERSION, rely on API negotiation, or upgrade the daemon to match the client.

This TypeScript error occurs when attempting to iterate over a value that does not implement the iterable protocol, such as using for...of on non-array types or union types containing non-iterable values.

This TypeScript error occurs when you try to assign a value that might be undefined to a variable expecting only a string type. It happens most often with optional properties, function parameters, or when strictNullChecks is enabled.

This error occurs when TypeScript's type narrowing eliminates all possible types from a union, leaving the impossible "never" type. It typically happens with typeof checks that exclude all valid type options.

This error occurs when a generic type parameter has constraints that contradict each other or when trying to use a constrained type in ways that conflict with its defined boundaries.

This error occurs when TypeScript cannot verify that a value matches an inferred type within a conditional type. It typically happens when using the infer keyword in complex conditional types where type narrowing is insufficient.