Copyright © 2020 Neo4j, Inc.
Documentation license: Creative Commons 4.0
This document lists the Neo4j status codes for Neo4j version 4.1.
Each status code follows the same format: Neo.[Classification].[Category].[Title].
The fact that a status code is returned by the server does always mean there is a fatal error.
Status codes can also indicate transient problems that may go away if you retry the request.
What the effect of the status code is can be determined by its classification.
| Classification | Description | Effect on transaction |
|---|---|---|
|
|
The Client sent a bad request - changing the request might yield a successful outcome. |
Rollback |
|
|
There are notifications about the request sent by the client. |
None |
|
|
The database cannot service the request right now, retrying later might yield a successful outcome. |
Rollback |
|
|
The database failed to service the request. |
Rollback |
This is a complete list of all status codes Neo4j may return, and what they mean.
| Status Code | Description |
|---|---|
|
|
The request cannot be processed by this server. Write requests can only be processed by the leader. |
|
|
The request referred to a database that does not exist. |
|
|
The request referred to a database that already exists. |
|
|
The request could not be completed due to 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 'dbms.memory.transaction.max_size' in the neo4j configuration (normally in 'conf/neo4j.conf' or, if you are using Neo4j Desktop, found through the user interface). |
|
|
Failed to invoke a procedure. See the detailed error description for 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 has not completed 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. |
|
|
Unable to perform operation because it would 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 would violate constraint |
|
|
Unable to perform operation because constraint with given name already exists. |
|
|
Unable to perform operation because an equivalent schema rule already exists. |
|
|
A requested operation can not be performed on the specified index because the index is part of a constraint. If you want to drop the index, for instance, you must drop the constraint. |
|
|
Unable to perform operation because it would 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 operation because index with given name already exists. |
|
|
Unable to create index or constraint because schema had a repeated label. |
|
|
Unable to create index or constraint because schema had a repeated property. |
|
|
Unable to create index or constraint because schema had a repeated relationship type. |
|
|
A token name, such as a label, relationship type or property key, used is not valid. 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 client is unauthorized due to authentication failure. |
|
|
The request could not be completed due to 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 system database. |
|
|
This is an administration command and it should be executed against the LEADER server of the system database. |
|
|
The statement refers to a parameter that was not provided in the request. |
|
|
The statement refers to a non-existent property. |
|
|
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. |
|
|
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. |
|
|
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 system database with bookmarks from another database. |
|
|
There were concurrent requests accessing the same transaction, which is not allowed. |
|
|
Transaction hook failure. |
|
|
Transaction was marked as both successful and failed. Failure takes precedence and so this transaction was rolled back although it may have looked like it was going to be committed |
|
|
The request referred to a transaction that does not exist. |
|
|
The transaction has not completed within the specified timeout (dbms.transaction.timeout). You may want to retry with a longer timeout. |
|
|
Transaction changes did not pass validation checks |
|
|
The query used a procedure that generated a warning. |
|
|
This query builds a cartesian product between disconnected patterns. |
|
|
Queries using dynamic properties will use neither index seeks nor index scans for those properties |
|
|
The execution plan for this query contains the Eager operator, which forces all dependent data to be materialized in main memory before proceeding |
|
|
Exhaustive shortest path has been planned for your query that means that shortest path graph algorithm might not be used to find the shortest path. Hence an exhaustive enumeration of all paths might be used in order to find the requested shortest path. |
|
|
This feature is experimental and should not be used in production systems. |
|
|
This feature is deprecated and will be removed in future versions. |
|
|
The database was unable to plan a hinted join. |
|
|
Adding a schema index may speed up this query. |
|
|
This query is not supported by the chosen runtime. |
|
|
Index cannot execute wildcard query efficiently |
|
|
The provided pattern is unbounded, consider adding an upper limit to the number of node hops. |
|
|
The provided label is not in the database. |
|
|
The provided property key is not in the database |
|
|
The provided relationship type is not in the 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 generate code for the query. A stacktrace can be found in the debug.log. |
|
|
The database was unable to execute the statement. |
|
|
The database was unable to execute a remote part of the statement. |
|
|
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. |
|
|
Replication failure. |
|
|
Unable to route the request to the appropriate server |
|
|
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 'dbms.memory.heap.max_size' in the neo4j configuration (normally in 'conf/neo4j.conf' or, if you are using Neo4j Desktop, found through the user interface) or if you are running an embedded installation increase the heap by using '-Xmx' command line flag, and then restart the database. |
|
|
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 2M, add `dbms.jvm.additional=-Xss2M' to in the neo4j configuration (normally in 'conf/neo4j.conf' or, if you are using Neo4j Desktop, found through the user interface) or if you are running an embedded installation just add -Xss2M as command line flag. |
|
|
There is not enough memory to perform the current task. Please try increasing 'dbms.memory.off_heap.max_size' in the neo4j configuration (normally in 'conf/neo4j.conf' or, if you are using Neo4j Desktop, found through the user interface), and then restart the database. |
|
|
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. |
|
|
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 lease under which this transaction was started is no longer valid. |
|
|
Unable to acquire lock within configured timeout (dbms.lock.acquisition.timeout). |
|
|
The transaction has been terminated, so no more locks can be acquired. This can occur because the transaction ran longer than the configured transaction timeout, or because a human operator manually terminated the transaction, or because the database is shutting down. |
|
|
Unable to start new transaction since the maximum number of concurrently executing transactions is reached (dbms.transaction.concurrent.maximum). You can retry at a later time or consider increasing allowed maximum of concurrent transactions. |
|
|
Transaction has seen state which has been invalidated by applied updates while transaction was active. Transaction may succeed if retried. |
|
|
Explicitly terminated by the user. |