Error map
57014 ERROR: canceling statement due to statement timeout
PostgreSQL · layer 5, Data
Centre: this error. First ring: errors it is linked with (12). 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.
Directly related (12)
API Request Timed Out (ETIMEDOUT / ReadTimeout / timeout of 30000ms exceeded)
The client gave up waiting — either for the connection to open or for the response to arrive.
Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. All pooled connections were in use and max pool size was reached.
The application’s connection pool was exhausted — all connections busy or leaked.
pg_restore: error: input file appears to be a text format dump. Please use psql.
A plain .sql dump was given to pg_restore, which only reads custom/directory/tar formats.
ERROR: current transaction is aborted, commands ignored until end of transaction block
An earlier statement in the same transaction failed; PostgreSQL rejects everything until you ROLLBACK.
SQL Server: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
The command ran longer than the client’s CommandTimeout (default 30 seconds).
pg_dump: error: aborting because of server version mismatch
Your pg_dump client is older than the server you’re dumping.
Lock wait timeout exceeded; try restarting transaction (MySQL 1205)
A query waited too long for a row lock held by another transaction and gave up.
AWS Lambda: Task timed out after X seconds
The function ran longer than its configured timeout (default 3 seconds) and Lambda stopped it.
TaskCanceledException: The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing
The HTTP call took longer than HttpClient.Timeout (100 s default), so .NET cancelled it.
ERROR: prepared statement "s1" already exists (PgBouncer transaction mode)
Named prepared statements collided — typically because PgBouncer in transaction pooling mode hands connections between clients.
FATAL: terminating connection due to idle-in-transaction timeout
A session opened a transaction and sat idle longer than idle_in_transaction_session_timeout.
API Gateway: {"message": "Endpoint request timed out"} (504 after 29 seconds)
The backend (usually Lambda) didn’t respond within API Gateway’s integration timeout (29 seconds by default for REST APIs).
Two steps away (34)
Error: connect ECONNREFUSED 127.0.0.1:5432
Nothing is listening at that host:port — the target service is down or you’re connecting to the wrong address.
HTTP 408 Request Timeout
The server closed the connection because the client took too long to send the complete request.
HTTP 504 Gateway Timeout
A proxy or gateway waited too long for the upstream server to respond and gave up.
Cloudflare Error 524: A Timeout Occurred
Cloudflare connected to the origin, but the origin didn’t send an HTTP response within 100 seconds.
HTTP 304 Not Modified
The cached copy is still valid, so the server sends no body and the client reuses its cache.
HikariPool-1 - Connection is not available, request timed out after 30000ms
The connection pool was exhausted — all connections were busy for 30 seconds.
[nodemon] app crashed - waiting for file changes before starting...
Your app threw an error on startup; nodemon is waiting for a file change to retry.
npm ERR! could not determine executable to run
npx couldn’t find a binary to run for that package.
ERROR: cannot drop table x because other objects depend on it
Views, foreign keys or other objects depend on what you’re dropping.
Deadlock found when trying to get lock; try restarting transaction
Two transactions waited on each other’s locks; the database killed one so the other could continue.
MySQL ERROR 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
MySQL detected a deadlock between two transactions and rolled one back.
ERROR: could not serialize access due to concurrent update
A REPEATABLE READ/SERIALIZABLE transaction conflicted with a concurrent one and must be retried.
SQL Server: Login failed for user 'x'. (Error 18456)
SQL Server rejected the login — wrong password, wrong authentication mode, or a disabled/missing login.
SQL Server: Invalid column name 'x'. (Msg 207)
SQL Server can’t find the column — typo, missing migration, or a string in double quotes with QUOTED_IDENTIFIER ON.
SQL Server: Violation of PRIMARY KEY constraint 'x'. Cannot insert duplicate key in object 'y'. (Msg 2627)
An insert duplicated a primary key or unique constraint value.
ERROR: bind message supplies 2 parameters, but prepared statement requires 1
The number of query parameters sent doesn’t match the $1, $2 … placeholders in the SQL.
'react-scripts' is not recognized as an internal or external command / react-scripts: command not found
node_modules is missing or broken, so the react-scripts binary isn’t available.
MySQL ERROR 2006 (HY000): MySQL server has gone away
The connection to MySQL was closed — usually by a timeout or a packet larger than `max_allowed_packet`.
MySQL ERROR 1040 (08004): Too many connections
MySQL reached `max_connections` and refuses new clients.
sqlite3.OperationalError: database is locked (SQLITE_BUSY)
Another connection holds a write lock on the SQLite file, and this one gave up waiting.
AWS: ThrottlingException / Rate exceeded
You exceeded the request rate for an AWS API; retry with exponential backoff.
java.util.concurrent.TimeoutException
A Future.get(timeout) or async operation didn’t complete in the allowed time.
MySQL ERROR 2013 (HY000): Lost connection to MySQL server during query
The connection dropped mid-query — server crash/restart, timeouts, or a proxy cutting long queries.
HTTP 499 Client Closed Request (Nginx)
Nginx-specific code logged when the client disconnected before the server finished responding.
PHP Fatal error: Maximum execution time of 30 seconds exceeded
The script ran longer than `max_execution_time` and PHP stopped it.
Cloudflare Error 522: Connection Timed Out
Cloudflare’s TCP connection to your origin timed out — the origin didn’t answer at all.
PostgreSQL: ERROR: column "x" does not exist
PostgreSQL can’t find the column — a missing migration, a case-sensitive quoted name, or a string literal written in double quote…
ERROR: column "x" of relation "y" already exists
ALTER TABLE ADD COLUMN for a column that’s already there.
Error Domain=NSURLErrorDomain Code=-1001 "The request timed out."
The server didn’t respond within URLSession’s timeout (60 s default) — slow server, unreachable host on this network, or a stalle…
gRPC Error: 4 DEADLINE_EXCEEDED: Deadline exceeded
The call didn’t complete before the client’s deadline — slow server, network issues, or a deadline that’s too short.
Nginx: upstream timed out (110: Connection timed out) while reading response header from upstream
Nginx waited longer than proxy_read_timeout (60 s default) for the backend (app server, PHP-FPM) to respond, then returned 504.
cURL error 28: Operation timed out after 30001 milliseconds with 0 bytes received
A PHP cURL (or Guzzle) request timed out before the remote server answered.
API Gateway {"message": "Internal server error"} 502 — Malformed Lambda proxy response
The Lambda behind an API Gateway proxy integration returned something that isn’t the required {statusCode, headers, body} shape,…
API Gateway 403: User is not authorized to access this resource with an explicit deny
An API Gateway authorizer (Lambda/Cognito) or resource policy denied the request.
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError