Error map
COMMIT Changes disappear: transaction never committed (autocommit off, missing COMMIT)
SQL · layer 5, Data
Centre: this error. First ring: errors it is linked with (11). 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 (11)
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.
FATAL: terminating connection due to idle-in-transaction timeout
A session opened a transaction and sat idle longer than idle_in_transaction_session_timeout.
Inconsistent results inside a transaction: non-repeatable and phantom reads (isolation level)
Two reads in the same transaction see different data because another transaction committed in between.
SQL Server Msg 3902: The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION
A COMMIT (or ROLLBACK 3903) ran when no transaction was open, often after an earlier error rolled everything back.
Query returns far too many rows: accidental Cartesian product (missing JOIN condition)
Two tables were joined without a condition, so every row of one pairs with every row of the other.
CASE expression returns mixed types: conversion failed / types cannot be matched
The branches of a CASE expression produce incompatible data types (text and number, date and string).
COUNT(column) ignores NULLs: counts differ from COUNT(*)
`COUNT(col)` counts only non-NULL values, while `COUNT(*)` counts rows, so totals don't match.
SQL Server Msg 266: Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements
A stored procedure or trigger exited with a different @@TRANCOUNT than it started with.
SQLite: cannot start a transaction within a transaction
BEGIN was issued while a transaction was already open on the same connection.
Spanner: Session not found / ABORTED: transaction was aborted — retry the transaction
Spanner killed an idle session or aborted a transaction because of lock conflicts, and the client must retry.
Firestore: 10 ABORTED: Too much contention on these documents. Please try again.
Many transactions or writes hit the same document, so Firestore aborted yours.
Two steps away (32)
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`.
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 1040 (08004): Too many connections
MySQL reached `max_connections` and refuses new clients.
Cloudflare Error 522: Connection Timed Out
Cloudflare’s TCP connection to your origin timed out — the origin didn’t answer at all.
Cloudflare Error 524: A Timeout Occurred
Cloudflare connected to the origin, but the origin didn’t send an HTTP response within 100 seconds.
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.
java.util.ConcurrentModificationException
A collection was modified while being iterated (even in a single thread).
java.lang.InterruptedException (sleep interrupted)
A blocked thread (sleep, wait, join, queue take) was interrupted by another thread.
java.util.concurrent.TimeoutException
A Future.get(timeout) or async operation didn’t complete in the allowed time.
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.
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.
ERROR: canceling statement due to statement timeout
A query ran longer than statement_timeout and PostgreSQL cancelled it.
ERROR: out of shared memory — HINT: You might need to increase max_locks_per_transaction.
A transaction took more locks than the lock table can hold — usually touching many tables/partitions at once.
Performance: N+1 query problem (one query per row in a loop)
Code runs one query to load a list, then one more query per item — hundreds of queries per page.
AttributeError: 'X' object has no attribute 'y'
You accessed an attribute or method that doesn’t exist on that object type.
java.lang.ClassCastException: class A cannot be cast to class B
An object was cast to a type it isn’t.
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
A Node API got an argument of the wrong type — usually undefined because an env var or config value is missing.
ERROR: aggregate functions are not allowed in WHERE (use HAVING) / MySQL 1111 Invalid use of group function
An aggregate (SUM, COUNT, AVG) was used in WHERE, which filters rows before grouping.
WHERE col = NULL returns no rows (use IS NULL)
Comparing anything to NULL with = or never matches, because the result is UNKNOWN, not true.
NOT IN (subquery) returns no rows because the subquery contains NULL
If the list or subquery for NOT IN contains a single NULL, the whole condition is UNKNOWN and no rows come back.
SQL Server Msg 1205: Transaction was deadlocked on lock resources and has been chosen as the deadlock victim
Two sessions each hold locks the other needs, so SQL Server rolled one of them back.
SQL Server Msg 209: Ambiguous column name
A column exists in more than one table of the query and isn't qualified.
Cloud Build trigger doesn't fire or fails: GitHub connection/app not installed or repository not linked
A push or PR doesn't start a build, or the trigger shows a connection error with GitHub.
sqlite3.OperationalError: database is locked (SQLITE_BUSY)
Another connection holds a write lock on the SQLite file, and this one gave up waiting.
sqlite3.IntegrityError: UNIQUE constraint failed: users.email
An insert/update duplicated a value in a UNIQUE or PRIMARY KEY column in SQLite.
sqlite3.IntegrityError: NOT NULL constraint failed: table.column
A NULL went into a NOT NULL column in SQLite.
Firestore: 4 DEADLINE_EXCEEDED: Deadline exceeded / 14 UNAVAILABLE: The service is currently unavailable
A Firestore request timed out or could not reach the service — contention, hot documents, large operations or network issues.
Firebase Storage: storage/retry-limit-exceeded — Max retry time for operation exceeded
An upload or download kept failing until the SDK's retry window (default 2 minutes for uploads) ran out.
Firestore: 3 INVALID_ARGUMENT: The value of property "data" is longer than 1048487 bytes / Document exceeds the maximum size
A single Firestore document (all fields combined) went beyond the 1 MiB limit.
Firestore: 6 ALREADY_EXISTS — document already exists (create() on an existing document)
`create()` or a transaction tried to create a document at a path that is already taken.
Firestore write latency/errors: hotspotting from sequential document IDs or indexed fields
Writes get slow or fail when many documents with monotonically increasing IDs or indexed values land in the same key range.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError