List of all error codes
This page contains lists of all Neo4j errors, grouped by type.
Client errors
This is a complete list of all client errors Neo4j may return, and what they mean.
| Neo4j status code | Description |
|---|---|
|
Invalid change identifier. |
|
The request cannot be processed by this server. Write requests can only be processed by the leader. |
|
Unable to route the request to the appropriate server |
|
The request referred to a database that does not exist. |
|
The request referred to a database with an alias. |
|
The request referred to a database that already exists. |
|
An illegal chain of aliases has been detected. This request cannot be executed. |
|
The request could not be completed due to an access mode violation |
|
This is a read-only database, writing or modifying the database is not allowed. |
|
The request contained fields that were empty or are not allowed. |
|
The transaction used more memory than was allowed.
The maximum allowed size for a transaction can be configured with |
|
This transaction required the database to be of a higher kernel version than it is. Make sure that the Neoj4 DBMS has been correctly upgraded before retrying this operation. |
|
This database is in read-only mode, writing or modifying the database is not allowed. |
|
Failed to invoke a procedure. See the detailed error description for the exact cause. |
|
A request referred to a procedure that is not registered with this database instance. If you are deploying custom procedures in a cluster setup, ensure all instances in the cluster have the procedure jar file deployed. |
|
The database failed to register a procedure, refer to the associated error message for details. |
|
The procedure did not complete within the specified timeout. You may want to retry with a longer timeout. |
|
A procedure is using or receiving a value of an invalid type. |
|
The client provided an invalid request. |
|
The client provided a request that was missing required fields or had values that are not allowed. |
|
The client made a request but did not consume outgoing buffers in a timely fashion. |
|
Server is in panic. |
|
Failed to route. |
|
Unable to perform this operation because it will clash with a pre-existing constraint. |
|
The request (directly or indirectly) referred to a constraint that does not exist. |
|
A constraint imposed by the database was violated. |
|
Added or changed index entry violates a constraint. |
|
Unable to perform this operation because a constraint with that name already exists. |
|
Unable to perform this operation because an equivalent schema rule already exists. |
|
A requested operation cannot be performed on the specified index because the index is part of a constraint. If you want to drop the index, you must also drop the constraint. |
|
Unable to perform this operation because it will clash with a pre-existing index. |
|
The request referenced an index by its schema and multiple matching indexes were found. |
|
The request did not contain the properties required by the index. |
|
The request (directly or indirectly) referred to an index that does not exist. |
|
Unable to perform this operation because an index with that name already exists. |
|
Unable to create an index or a constraint because the schema had a repeated label. |
|
Unable to create an index or a constraint because the schema had a repeated property. |
|
Unable to create an index or a constraint because the schema had a repeated relationship type. |
|
An invalid name is used for a token (label, relationship type, property key). Tokens cannot be empty strings and cannot be null. |
|
The client has provided incorrect authentication details too many times in a row. |
|
The stored authorization info has expired. Please reconnect. |
|
The credentials have expired and need to be updated. |
|
An attempt was made to perform an unauthorized action. |
|
The auth provider token has expired. |
|
The client is unauthorized due to authentication failure. |
|
The request could not be completed due to an access mode violation. |
|
The statement is attempting to perform operations using invalid arguments. |
|
Invalid use of arithmetic, such as dividing by zero. |
|
A constraint imposed by the statement is violated by the data in the database. |
|
The statement refers to a non-existent entity. |
|
Access to an external resource failed. |
|
This is an administration command and it should be executed against the |
|
The statement refers to a parameter that was not provided in the request. |
|
The statement refers to a non-existent property. |
|
The database was unable to execute a remote part of the statement due to a client error. |
|
This query is not supported by the chosen runtime. |
|
The statement is syntactically valid but expresses something that the database cannot do. |
|
The statement contains invalid or unsupported syntax. |
|
The statement is attempting to perform operations on values with types that are not supported by the operation. |
|
This administration command is not supported. |
|
This query performed an operation that is not supported in this context. |
|
The transaction is of the wrong type to service the request. For instance, a transaction that has had schema modifications performed in it cannot be used to subsequently perform data operations, and vice versa. |
|
The supplied bookmark cannot be interpreted. You should only supply a bookmark that was previously generated by Neo4j. Maybe you have generated your own bookmark, or modified a bookmark since it was generated by Neo4j. |
|
Mixing bookmarks generated by different databases is forbidden.
You should only chain bookmarks that are generated from the same database.
You may however chain bookmarks generated from the |
|
The transaction has been terminated, so no more locks can be acquired. This may occur because the transaction ran longer than the configured transaction timeout, a human operator manually terminated the transaction, or the database shut down. |
|
Explicitly terminated by the user. |
|
There were concurrent requests accessing the same transaction, which is not allowed. |
|
Transaction hook failure. |
|
The transaction was marked as both successful and failed. Because failure takes precedence, the transaction was rolled back. |
|
The request referred to a transaction that does not exist. |
|
The transaction has not completed within the specified timeout ( |
|
The transaction has not completed within the timeout specified at its start by the client. You may want to retry with a longer timeout. |
|
Transaction changes did not pass validation checks. |
Transient errors
This is a complete list of all transient errors Neo4j may return, and what they mean.
| Neo4j status code | Description |
|---|---|
|
Change identifier points to a future transaction that has not yet happened on this database instance. |
|
Replication failure. |
|
The database is not currently available to serve your request, refer to the database logs for more details. Retrying your request at a later time may succeed. |
|
The memory pool limit was exceeded. The corresponding setting can be found in the error message. |
|
There is not enough memory to perform the current task.
Please try increasing If you are running an embedded installation, you can increase the heap by using the |
|
There is not enough stack size to perform the current task. This is generally considered to be a database error, so please contact Neo4j support. You could try increasing the stack size; for example to set the stack size to If you are running an embedded installation, you can add |
|
There is not enough memory to perform the current task.
Please try increasing |
|
There are no available threads to serve this request at the moment. You can retry at a later time, or consider increasing max thread pool size for bolt connector(s). |
|
An auth provider request failed. |
|
An auth provider request timed out. |
|
The user was modified concurrently to this request. |
|
The database was unable to execute the statement in a timely fashion. |
|
The database was unable to execute a remote part of the statement due to a transient failure. |
|
Bookmark wait timed out. Database has not reached the specified version. |
|
Database constraints changed since the start of this transaction. |
|
This transaction, and at least one more transaction, has acquired locks in a way that it will wait indefinitely, and the database has aborted it. Retrying this transaction will most likely be successful. |
|
Interrupted while waiting. |
|
The request could not be completed due to cluster leader switch. |
|
The lease under which this transaction was started is no longer valid. |
|
Unable to acquire lock within configured timeout ( |
|
Unable to start new transaction since the maximum number of concurrently executing transactions is reached ( |
|
Transaction has seen state which has been invalidated by applied updates while the transaction was active. Transaction may succeed if retried. |
|
The transaction was marked as failed because a query failed. |
Database error
This is a complete list of all database errors Neo4j may return, and what they mean.
| Neo4j status code | Description |
|---|---|
|
Change Data Capture is not currently enabled for this database. |
|
Unable to read the Change Data Capture data for this database. |
|
The limit to number of databases has been reached. |
|
Unable to start database. |
|
Unknown database management error. |
|
The database was unable to execute a remote part of the statement. |
|
The request (directly or indirectly) referred to an index that is in a failed state. The index needs to be dropped and recreated manually. |
|
A malformed schema rule was encountered. Please contact your support representative. |
|
Expected set of files not found on disk. Please restore from backup. |
|
An unknown error occurred. |
|
Creating a requested constraint failed. |
|
The database failed to drop a requested constraint. |
|
Failed to create an index. |
|
The database failed to drop a requested index. |
|
The request accessed a label that did not exist. |
|
The request accessed a property that does not exist. |
|
The request accessed a relationship type that does not exist. |
|
The request referred to a schema rule that does not exist. |
|
The request referred to a schema rule that is defined multiple times. |
|
The maximum number of tokens of this type has been reached, no more tokens of this type can be created. |
|
The database was unable to execute the statement. |
|
The database was unable to execute a remote part of the statement. |
|
The transaction was terminated because another transaction executing the same query encountered an error. |
|
The database was unable to commit the transaction. |
|
The database was unable to write transaction to log. |
|
The database was unable to roll back the transaction. |
|
The database was unable to start the transaction. |
|
The database was unable to terminate the transaction. |