// error codes
Error codes in AI-built apps, explained
Paste or type the code you see. Each entry says what it means, why an AI-built app usually hits it, and the first thing to check.
40 codes
Supabase data API
-
PGRST116The request asked for exactly one row, but the query returned zero rows or more than one, so the API answered with HTTP 406. The details field says how many, for example "The result contains 0 rows". -
PGRST200The query tried to embed one table inside another in a single request, but the API knows no foreign key between them. Either the relationship does not exist, or the API's schema cache is out of date. -
PGRST202The app called a database function through the API, but no function with that name and those argument names was found. The function may not exist, or the schema cache has not picked up a recent change to it. -
PGRST204The request named a column that the API cannot find on that table, so it was rejected with HTTP 400. The column does not exist, or the schema cache does not know about it yet. -
PGRST205The request named a table that the API cannot find, so it answered with HTTP 404. The table does not exist in that schema, or the schema cache has not caught up with it yet. -
PGRST301The token sent in the Authorization header could not be decoded or is not valid, so the API rejected the request with HTTP 401. -
PGRST303The token could be read, but its claims did not pass validation, for example because it has expired. The API rejects the request with HTTP 401.
Postgres
-
42501SQLSTATE 42501 is insufficient_privilege: the current database role is not allowed to do what the query asked on this table. -
23505SQLSTATE 23505 is unique_violation: the row would repeat a value in a column, or set of columns, that must be unique, such as a primary key or an email column. -
23503SQLSTATE 23503 is foreign_key_violation: the row points at a row in another table that does not exist, or a delete would leave other rows pointing at nothing. -
23502SQLSTATE 23502 is not_null_violation: the row leaves a required column empty (null), and that column is declared NOT NULL. -
42P01SQLSTATE 42P01 is undefined_table: the SQL refers to a table, or view, that the database cannot find under that name. -
42703SQLSTATE 42703 is undefined_column: the query names a column that the table does not have. -
22P02SQLSTATE 22P02 is invalid_text_representation: a value arrived as text that cannot be read as the column's type, for example a string that is not a valid UUID. -
25006SQLSTATE 25006 is read_only_sql_transaction: the database only accepts reads right now, so writes fail. On Supabase this code appears when the project has entered read-only mode because of its disk or database size.
Supabase Auth
-
invalid_credentialsSupabase Auth did not recognize the login details or the grant type sent with the sign-in request, so no session was created. -
email_not_confirmedThe user exists, but signing in is not allowed because the email address has not been confirmed yet. -
over_email_send_rate_limitSupabase Auth refused to send another email, such as a sign-up confirmation or a magic link, because too many emails have been sent. The user has to wait a while before trying again. -
user_already_existsSupabase Auth cannot create this user because an account with the same email address or phone number already exists. -
otp_expiredThe one-time code or email link for this sign-in has expired or is not valid, so Supabase Auth refused it. The user has to sign in again to get a new one.
Vercel
-
FUNCTION_INVOCATION_TIMEOUTA Vercel Function took longer than its allowed execution time, so Vercel stopped waiting and returned 504 Gateway Timeout. -
FUNCTION_INVOCATION_FAILEDThe function failed while handling the request, for example because its runtime process crashed or the code threw an error that nothing caught, so Vercel returned 500 Internal Server Error. -
FUNCTION_PAYLOAD_TOO_LARGEThe data sent in the request body to a Vercel Function is larger than the allowed size, so the request is refused with 413. Vercel documents the limit as 4.5 MB. -
NOT_FOUNDVercel could not find what was requested at this URL. The resource may have been moved or deleted, or the URL may contain a typo. -
DEPLOYMENT_NOT_FOUNDThe request went to a Vercel deployment that does not exist, because the deployment URL or ID is wrong or the deployment has been deleted. -
DEPLOYMENT_PAUSEDVercel is not serving this deployment because it has been paused, for example by your spend management settings, an account limit, or a terms of service issue. The response is 503 Service Unavailable. -
MIDDLEWARE_INVOCATION_FAILEDThe Routing Middleware that runs before your pages failed while handling the request, for example because of an unhandled error in its code, so Vercel returned 500 Internal Server Error.
Netlify
-
Page not foundNetlify found no file to serve at this path and showed its default 404 page. In a single-page app only index.html exists, so any other path gets this page unless a rewrite rule serves index.html instead. -
non-zero exit code: 2The build command failed, so Netlify stopped and did not deploy. The exit code is only a summary; the actual reason is printed in the build log above it.
Firebase
-
auth/invalid-api-keyFirebase Auth rejected the API key in the app's Firebase config as invalid. The key has to be copied exactly from the Firebase console. -
auth/unauthorized-domainThe domain the app is running on is not authorized for OAuth operations in this Firebase project, so sign-in with a provider such as Google is blocked there. -
auth/invalid-credentialThe sign-in details were not accepted. For email and password sign-in, Firebase returns this code for a wrong email or password when email enumeration protection is on. -
permission-deniedThe caller does not have permission to run this read or write. For apps that use the client SDK, that decision comes from the project's Firestore Security Rules. -
failed-preconditionFirestore rejected the operation because the system is not in the state the operation needs. A common case is a query that needs a composite index that does not exist yet. -
storage/unauthorizedThe user is not authorized to do the requested action on this file. The project's Cloud Storage Security Rules refused it.
HTTP status codes
-
401The request was refused because it does not carry valid authentication credentials for the resource. The server expects the client to authenticate first. -
403The server understood the request but refuses to process it. Unlike 401, signing in again makes no difference, because the problem is permission for this resource or action. -
404The server cannot find the requested resource. A 404 does not say whether the resource is missing for now or for good. -
429The client sent too many requests in a given amount of time, and the server is asking it to slow down. The response may include a Retry-After header that says how long to wait. -
504A server acting as a gateway or proxy did not get a response in time from the server behind it, so it gave up and returned 504.
No code here matches that yet.