21.2. Neo4j Status Codes
The transactional endpoint may in any response include zero or more status codes, indicating issues or information for the client. 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.
This is not the same thing as HTTP status codes. Neo4j Status Codes are returned in the response body, at the very end of the response.
|Classification||Description||Effect on transaction|
The Client sent a bad request - changing the request might yield a successful outcome.
There are notifications about the request sent by the client.
The database failed to service the request.
The database cannot service the request right now, retrying later might yield a successful outcome.
This is a complete list of all status codes Neo4j may return, and what they mean.
This is a read only database, writing or modifying the database is not allowed.
The request (directly or indirectly) referred to a index that does not exist.
The client provided an invalid request.
The client provided a request that was missing required fields, or had values that are not allowed.
Unable to perform operation because it would clash with a pre-existing constraint.
Unable to create constraint because data that exists in the database violates it.
A constraint imposed by the database was violated.
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.
Unable to perform operation because it would clash with a pre-existing index.
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.
The maximum number of index entries supported has been reached, no more entities can be indexed.
The maximum number of labels supported has been reached, no more labels can be created.
The request (directly or indirectly) referred to a constraint that does not exist.
The request (directly or indirectly) referred to an index that does not exist.
The client provided an incorrect username and/or password.
The client has provided incorrect authentication details too many times in a row.
The client does not have privileges to perform the operation requested.
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 is directly referring to an entity that does not exist.
The statement is attempting to perform operations using invalid arguments
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 statement is referring to a label that does not exist.
The statement is referring to a property that does not exist.
The statement is referring to a parameter that was not provided in the request.
There were concurrent requests accessing the same transaction, which is not allowed.
A transaction event handler threw an exception. The transaction will be rolled back.
Transaction hook failure.
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.
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.
Transaction changes did not pass validation checks
This query builds a cartesian product between disconnected patterns.
This feature is deprecated and will be removed in future versions.
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
Adding a schema index may speed up this query.
The database was unable to plan a hinted join.
Queries with join hints are not supported by the RULE planner.
This query is not supported by the COST planner.
This query is not supported by the compiled runtime.
A malformed schema rule was encountered. Please contact your support representative.
The request (directly or indirectly) referred to an index that is in a failed state. The index needs to be dropped and recreated manually.
An unknown failure occurred.
Creating a requested constraint failed.
The database failed to drop a requested constraint.
The request referred to a schema rule that defined multiple times.
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 database was unable to execute the statement.
The database was unable to start the transaction.
The database was unable to commit the transaction.
The database was unable to roll back the transaction.
The database was unable to write transaction to log.
The transaction was unable to release one or more of its locks.
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.
An unknown network failure occurred, a retry may resolve the issue.
The database schema was modified while this transaction was running, the transaction should be retried.
The user was modified concurrently to this request.
The external resource is not available
The transaction was unable to acquire a lock, for instance due to a timeout or the transaction thread being interrupted.
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.