List of GQLSTATUS error codes

The following page provides an overview of all GQLSTATUS server error codes in Neo4j. All errors in Neo4j have severity level ERROR.

Warning

Please note that while GQLSTATUS codes remain stable (any changes to them will be breaking), changes to status descriptions associated with these codes are not breaking and may happen at any time. For this reason, parsing the status descriptions or incorporating them into scripts is not recommended.

Connection exceptions

Connection exceptions occur when the client (e.g. Browser/Bloom/Cypher Shell) is unable to connect to the server for various reasons such as network issues, server-side routing being disabled, or the database being unavailable, etc.

08000

Status description: error: connection exception

08007

Status description: error: connection exception - transaction resolution unknown

08N00

Status description: error: connection exception - unable to connect to database. Unable to connect to database { [db] }. Unable to get bolt address of the leader. Check the status of the database. Retrying your request at a later time may succeed.

08N01

Status description: error: connection exception - unable to write to database. Unable to write to database { [db] } on this server. Server-side routing is disabled. Either connect to the database leader directly or enable server-side routing by setting { [cfgSetting] }=true.

08N02

Status description: error: connection exception - unable to connect to database. Unable to connect to database { [db] }. Server-side routing is disabled. Either connect to { $db } directly, or enable server-side routing by setting { [cfgSetting] }=true.

08N03

Status description: error: connection exception - failed to write to graph. Failed to write to graph { [graph] }. Check the defined access mode in both driver and database.

08N04

Status description: error: unable to route use clause. Routing with { [clause] } is not supported in embedded sessions. Connect to the database directly or try running the query using a Neo4j driver or the HTTP API.

08N05

Status description: error: connection exception - unable to route administration command. Routing administration commands is not supported in embedded sessions. Connect to the system database directly or try running the query using a Neo4j driver or the HTTP API.

08N06

Status description: error: connection exception - protocol error. General network protocol error.

08N07

Status description: error: connection exception - not the leader. This member is not the leader.

08N08

Status description: error: connection exception - database is read only. This database is read only on this server.

08N09

Status description: error: connection exception - database unavailable. The database { [db] } is currently unavailable. Check the database status. Retry your request at a later time.

08N10

Status description: error: connection exception - invalid server state. Message { [msg] } cannot be handled by session in the { [boltServerState] } state.

08N11

Status description: error: connection exception - request error. The request is invalid and could not be processed by the server. See cause for further details.

08N12

Status description: error: connection exception - failed to parse bookmark. Failed to parse the supplied bookmark. Verify it is correct or check the debug log for more information.

08N13

Status description: error: connection exception - database not up to requested bookmark. The database { [db] } is not up to the requested bookmark { [transactionId]1 }. The latest transaction ID is { $transactionId2 }.

08N14

Status description: error: connection exception - alias chains are not permitted. Unable to provide a routing table for the database identifed by the alias { [alias]1 } because the request comes from another alias { $alias2 } and alias chains are not permitted.

08N15

Status description: error: connection exception - no such routing policy. Policy definition of the routing policy { [routingPolicy] } could not be found. Verify that the spelling is correct.

08N16

Status description: error: connection exception - general driver client error. Remote execution failed with message { [msg] }.

08N17

Status description: error: connection exception - general driver transient error. Remote execution failed with message { [msg] }.

08N18

Status description: error: connection exception - general driver database error. Remote execution failed with message { [msg] }.

08N19

Status description: error: connection exception - shard execution transient error. Communication with shard { [graph] } failed with message { [msg] }.

08N20

Status description: error: connection exception - shard execution database error. Communication with shard { [graph] } failed with message { [msg] }.

08N21

Status description: error: connection exception - shard execution client error. Communication with shard { [graph] } failed with message { [msg] }.

Data exceptions

Data exceptions occur when a client request contains the wrong format, types, or other unsupported input. Some examples are data and constraint creation, which conflicts with existing constraints, properties of non-storable type, and spatial and temporal values with invalid components.

22000

Status description: error: data exception

22003

Status description: error: data exception - numeric value out of range. The numeric value { [value] } is outside the required range.

22004

Status description: error: data exception - null value not allowed

22007

Status description: error: data exception - invalid date, time, or datetime format

22012

Status description: error: data exception - division by zero

22015

Status description: error: data exception - interval field overflow

22G03

Status description: error: data exception - invalid value type

22G05

Status description: error: data exception - invalid date, time, or datetime function field name

22G0I

Status description: error: data exception - invalid duration field. { [field] } is not a valid duration field.

22N00

Status description: error: data exception - unsupported value. The provided value is unsupported and cannot be processed.

22N01

Status description: error: data exception - invalid type. Expected the value { [value] } to be of type { [valueTypeList] }, but was of type { [valueType] }.

22N02

Status description: error: data exception - specified negative numeric value. Expected { [option] } to be a positive number but found { [value] } instead.

22N03

Status description: error: data exception - specified numeric value out of range. Expected { [component] } to be of type { [valueType] } and in the range { [lower] } to { [upper] } but found { [value] }.

22N04

Status description: error: data exception - invalid input value. Invalid input { [input] } for { [context] }. Expected { [inputList] }.

22N05

Status description: error: data exception - input failed validation. Invalid input { [input] } for { [context] }.

22N06

Status description: error: data exception - required input missing. Invalid input. { [inputList] } needs to be specified.

22N07

Status description: error: data exception - invalid pre-parser option key. Invalid pre-parser option(s): { [optionList] }.

22N08

Status description: error: data exception - invalid pre-parser combination. Invalid pre-parser option, cannot combine { [option]1 } with { $option2 }.

22N09

Status description: error: data exception - conflicting pre-parser combination. Invalid pre-parser option, cannot specify multiple conflicting values for { [option] }.

22N10

Status description: error: data exception - invalid pre-parser option value. Invalid pre-parser option, specified { [input] } is not valid for option { [option] }. Valid options are: { [optionList] }.

22N11

Status description: error: data exception - invalid argument. Invalid argument: cannot process { [input] }.

22N12

Status description: error: data exception - invalid date, time, or datetime format. Invalid argument: cannot process { [input] }.

22N13

Status description: error: data exception - invalid time zone. Specified time zones must include a date component.

22N14

Status description: error: data exception - invalid temporal value combination. Cannot select both { [temporal]1 } and { $temporal2 }.

22N15

Status description: error: data exception - invalid temporal component. Cannot read the specified { [component] } component from { [temporal] }.

22N16

Status description: error: data exception - invalid import value. Importing entity values to a graph with a USE clause is not supported. Attempted to import { [expr] } to { [graph] }.

22N18

Status description: error: data exception - incomplete spatial value. A { [crs] } POINT must contain { [mapKeyList] }.

22N19

Status description: error: data exception - invalid spatial value. A POINT must contain either x and y, or latitude and longitude.

22N20

Status description: error: data exception - invalid spatial value dimensions. Cannot create POINT with { [dim]1 }D coordinate reference system (CRS) and { [value] } coordinates. Use the equivalent { $dim2 }D coordinate reference system instead.

22N21

Status description: error: data exception - unsupported coordinate reference system. Unsupported coordinate reference system (CRS): { [crs] }.

22N22

Status description: error: data exception - invalid spatial value combination. Cannot specify both coordinate reference system (CRS) and spatial reference identifier (SRID).

22N23

Status description: error: data exception - invalid latitude value. Cannot create WGS84 POINT with invalid coordinate: { [coordinates] }. The valid range for the latitude coordinate is [-90, 90].

22N24

Status description: error: data exception - invalid coordinate arguments. Cannot construct a { [valueType] } from { [coordinates] }.

22N25

Status description: error: data exception - invalid temporal arguments. Cannot construct a { [valueType] } from { [temporal] }.

22N26

Status description: error: data exception - unsupported rounding mode. Unknown rounding mode. Valid values are: CEILING, FLOOR, UP, DOWN, HALF_EVEN, HALF_UP, HALF_DOWN, UNNECESSARY.

22N27

Status description: error: data exception - invalid entity type. Invalid input { [input] } for { [context] }. Expected to be { [valueTypeList] }.

22N28

Status description: error: data exception - overflow error. The result of the operation { [operation] } has caused an overflow.

22N29

Status description: error: data exception - unknown coordinate reference system. Unknown coordinate reference system (CRS).

22N30

Status description: error: data exception - missing temporal unit. At least one temporal unit must be specified.

22N31

Status description: error: data exception - invalid properties in merge pattern. The { [entityType] } property { [propKey] } in { [pat] } is invalid. MERGE cannot be used with a graph element property value that is { [value] }.

22N32

Status description: error: data exception - non-deterministic sort expression. ORDER BY expressions must be deterministic.

22N33

Status description: error: data exception - invalid shortest path expression. Shortest path expressions must contain start and end nodes. Cannot find: { [variable] }.

22N34

Status description: error: data exception - invalid use of aggregate function. Cannot use { [funType] } function inside an aggregate function.

22N35

Status description: error: data exception - invalid date format. Cannot parse { [input] } as a DATE. Calendar dates need to be specified using the format YYYY-MM, while ordinal dates need to be specified using the format YYYY-DDD.

22N36

Status description: error: data exception - invalid temporal format. Cannot parse { [input] } as a { [valueType] }.

22N37

Status description: error: data exception - invalid coercion. Cannot coerce { [value] } to { [valueType] }.

22N38

Status description: error: data exception - invalid function argument. Invalid argument to the function { [fun] }.

22N39

Status description: error: data exception - unsupported property value type. Value { [value] } cannot be stored in properties.

22N40

Status description: error: data exception - non-assignable temporal component. Cannot assign { [component] } of a { [valueType] }.

22N41

Status description: error: data exception - merge node uniqueness constraint violation. The MERGE clause did not find a matching node { [variable] } and cannot create a new node due to conflicts with existing uniqueness constraints.

22N42

Status description: error: data exception - merge relationship uniqueness constraint violation. The MERGE clause did not find a matching relationship { [variable] } and cannot create a new relationship due to conflicts with existing uniqueness constraints.

22N43

Status description: error: data exception - unable to load external resource. Could not load external resource from { [url] }.

22N44

Status description: error: data exception - parallel runtime disabled. Parallel runtime has been disabled, enable it or upgrade to a bigger Aura instance.

22N46

Status description: error: data exception - unsupported use of parallel runtime. Parallel runtime does not support updating queries or a change in the state of transactions. Use another runtime.

22N47

Status description: error: data exception - invalid parallel runtime configuration. No workers are configured for the parallel runtime. Set server.cypher.parallel.worker_limit to a larger value.

22N48

Status description: error: data exception - unable to use specified runtime. Cannot use the specified runtime { [runtime] } due to { [cause] } not being supported. Use another runtime.

22N49

Status description: error: data exception - CSV buffer size overflow. Cannot read a CSV field larger than the set buffer size. Ensure the field does not have an unterminated quote, or increase the buffer size via dbms.import.csv.buffer_size.

22N51

Status description: error: data exception - graph reference not found. A graph reference with the name { [db] } was not found. Verify that the spelling is correct.

22N52

Status description: error: data exception - invalid combination of PROFILE and EXPLAIN. PROFILE and EXPLAIN cannot be combined.

22N53

Status description: error: data exception - invalid use of PROFILE. Cannot PROFILE query before results are materialized.

22N54

Status description: error: data exception - invalid map. Multiple conflicting entries specified for { [mapKey] }.

22N55

Status description: error: data exception - required key missing from map. Map requires key { [mapKey] } but was missing from field { [field] }.

22N56

Status description: error: data exception - protocol message length limit overflow. Protocol message length limit exceeded (limit: { [boltMsgLenLimit] }).

22N57

Status description: error: data exception - invalid protocol type. Protocol type is invalid. Invalid number of struct components (received { [count]1 } but expected { [count]2 }).

22N58

Status description: error: data exception - invalid spatial component. Cannot read the specified { [component] } component from { [value] }.

22N59

Status description: error: data exception - token does not exist. The { [tokenType] } token with id { [tokenId] } does not exist.

22N60

Status description: error: data exception - illegal element. Encountered illegal { [item] } element. Reason: { [msg] }

22N62

Status description: error: data exception - relationship type does not exist. The relationship type { [relType] } does not exist.

22N63

Status description: error: data exception - property key does not exist. The property key { [propKey] } does not exist.

22N64

Status description: error: data exception - constraint does not exist. The constraint { [constrDescrOrName] } does not exist.

22N65

Status description: error: data exception - equivalent constraint already exists. An equivalent constraint already exists: { [constrDescrOrName] }.

22N66

Status description: error: data exception - conflicting constraint already exists. A conflicting constraint already exists: { [constrDescrOrName] }.

22N67

Status description: error: data exception - duplicated constraint name. A constraint with the same name already exists: { [constr] }.

22N68

Status description: error: data exception - dependent constraint managed individually. Dependent constraints cannot be managed individually and must be managed together with its graph type.

22N69

Status description: error: data exception - index does not exist. The index { [idxDescrOrName] } does not exist.

22N70

Status description: error: data exception - equivalent index already exists. An equivalent index already exists: { [idxDescrOrName] }.

22N71

Status description: error: data exception - duplicated index name. An index with the same name already exists: { [idx] }.

22N73

Status description: error: data exception - constraint conflicts with existing index. Constraint conflicts with already existing index { [idxDescrOrName] }.

22N74

Status description: error: data exception - index conflicts with existing constraint. An index that belongs to the constraint { [constr] } contains a conflicting index.

22N75

Status description: error: data exception - constraint contains duplicated tokens. The constraint specified by { [constrDescrOrName] } includes a label, relationship type, or property key with name { [token] } more than once.

22N76

Status description: error: data exception - index contains duplicated tokens. The index specified by { [idxDescrOrName] } includes a label, relationship type, or property key with name { [token] } more than once.

22N77

Status description: error: data exception - property presence verification failed. { [entityType] } ({ [entityId] }) with { [tokenType] } { [token] } must have the following properties: { [propKeyList] }.

22N78

Status description: error: data exception - property type verification failed. { [entityType] } ({ [entityId] }) with { [tokenType] } { [token] } must have the property { [propKey] } with value type { [valueType] }.

22N79

Status description: error: data exception - property uniqueness constraint violated. Property uniqueness constraint violated: { [reasonList] }.

22N80

Status description: error: data exception - index entry conflict. Index entry conflict: { [value] }.

22N81

Status description: error: data exception - expression type unsupported here. Invalid input: { [exprType] } is not supported in { [context] }.

22N82

Status description: error: data exception - input contains invalid characters. Input { [input] } contains invalid characters for { [context] }. Special characters may require that the input is quoted using backticks.

22N83

Status description: error: data exception - input consists of too many components. Expected name to contain at most { [upper] } components separated by '.'.

22N84

Status description: error: data exception - string too long. Expected the string to be no more than { [upper] } characters long.

22N85

Status description: error: data exception - string too short. Expected the string to be at least { [lower] } characters long.

22N86

Status description: error: data exception - numeric range 0 disallowed. Expected a nonzero number.

22N88

Status description: error: data exception - not a valid CIDR IP. { [input] } is not a valid CIDR IP.

22N89

Status description: error: data exception - new password cannot be the same as the old password. Expected the new password to be different from the old password.

22N90

Status description: error: data exception - property type unsupported in constraint. { [valueType] } is not supported in property type constraints.

22N91

Status description: error: data exception - cannot convert alias local to remote or remote to local. Failed to alter the specified database alias { [alias] }. Altering remote alias to a local alias or vice versa is not supported. Drop and recreate the alias instead.

22N92

Status description: error: data exception - missing RETURN. This query requires a RETURN clause.

22N93

Status description: error: data exception - missing YIELD. A required YIELD clause is missing.

22N94

Status description: error: data exception - invalid YIELD *. YIELD * is not supported in this context. Explicitly specify which columns to yield.

22N95

Status description: error: data exception - parsing JSON exception. Invalid JSON input. Please check the format.

22N96

Status description: error: data exception - mapping JSON exception. Unable to map the JSON input. Please verify the structure.

22N97

Status description: error: data exception - unexpected struct tag. Unexpected struct tag: { [value] }.

22N98

Status description: error: data exception - wrong first field during deserialization. Unable to deserialize request. Expected first field to be { [field] }, but was { [value] }.

22N99

Status description: error: data exception - wrong token during deserialization. Unable to deserialize request. Expected { [token] }, found { [value] }.

22NA0

Status description: error: data exception - invalid property-based access control rule. Failed to administer property rule.

22NA1

Status description: error: data exception - invalid property-based access control rule involving non-commutative expressions. The property { [propKey] } must appear on the left hand side of the { [operation] } operator.

22NA2

Status description: error: data exception - invalid property-based access control rule involving multiple properties. The expression: { [expr] } is not supported. Property rules can only contain one property.

22NA3

Status description: error: data exception - invalid property-based access control rule involving NaN. 'NaN' is not supported for property-based access control.

22NA4

Status description: error: data exception - invalid property-based access control rule involving comparison with NULL. The property value access rule pattern { [pred] } always evaluates to NULL.

22NA5

Status description: error: data exception - invalid property-based access control rule involving IS NULL. The property value access rule pattern { [pred] } always evaluates to NULL. Use IS NULL instead.

22NA6

Status description: error: data exception - invalid property-based access control rule involving IS NOT NULL. The property value access rule pattern { [pred] } always evaluates to NULL. Use IS NOT NULL instead.

22NA7

Status description: error: data exception - invalid property-based access control rule involving nontrivial predicates. The expression: { [expr] } is not supported. Only single, literal-based predicate expressions are allowed for property-based access control.

22NA8

Status description: error: data exception - parsing JSON failure. Underlying error: { [cause] }.

22NA9

Status description: error: data exception - unexpected map entry. Invalid input. Unexpected key { [mapKey] }, expected keys are { [mapKeyList] }.

22NAA

Status description: error: data exception - invalid list for property-based access control rule. The expression { [expr] } is not supported. Lists containing { [exprType] } values are not supported for property-based access control.

22NAB

Status description: error: data exception - mixed type list for property-based access control rule. The expression { [expr] } is not supported. All elements in a list must be literals of the same type for property-based access control.

22NAC

Status description: error: data exception - characters after quote in CSV field. Characters after an ending quote in a CSV field are not supported. See { [input] } at position { [pos] }. This is read as { [variable] }.

22NAD

Status description: error: data exception - missing end quote in CSV field. Missing end quote at position { [pos] } in { [input] }.

22NAE

Status description: error: data exception - multi-line field in illegal CSV context. Multi-line fields are illegal in this context. Verify that there is not a missing end quote in { [input] } at position { [pos] }.

22NB0

Status description: error: data exception - invalid property-based access control rule involving WHERE and IS NULL. The property value access rule pattern { [pred] } always evaluates to NULL. Use WHERE syntax in combination with IS NULL instead.

22NB1

Status description: error: data exception - type mismatch. Type mismatch: expected to be { [valueTypeList] } but was { [input] }.

22NB2

Status description: error: data exception - incompatible graph type dependence. Graph type { [graphTypeDependence]1 } constraint { [constrDescrOrName]1 } is incompatible with graph type { $graphTypeDependence2 } constraint { $constrDescrOrName2 } because they have different graph type dependence.

22NB3

Status description: error: data exception - token presence verification failed. { [entityType] } ({ [entityId] }) with { [tokenType]1 } { [token]1 } must have the { $tokenType2 } { $token2 }.

22NB4

Status description: error: data exception - endpoint label presence verification failed. Relationship ({ [entityId]1 }) with type { [relType] } requires its { [endpointType] } node ({ $entityId2 }) to have the label { [label] }.

22NB5

Status description: error: data exception - unsupported time zone identifier. Unknown time zone identifier { [input] }.

22NB6

Status description: error: data exception - input empty. Invalid input. { [item] } is not allowed to be an empty string.

22NB7

Status description: error: data exception - element id unsupported on composite database. It is not supported to create element ids on composite databases. Create the element id for { [entityType] } { <<$entityId>> } on the constituent instead.

22NB8

Status description: error: data exception - invalid Neo4j type. { [input] } is not a recognized Neo4j type.

22NB9

Status description: error: data exception - invalid inner list type. Lists cannot have { [typeDescription] } as an inner type in this context.

22NBA

Status description: error: data exception - omitting mandatory field for property type constraints for vectors. Property type constraints for vectors need to define both coordinate type and dimension.

22NBC

Status description: error: data exception - index belongs to constraint. Index belongs to constraint { [constrDescrOrName] }.

22NBD

Status description: error: data exception - unsupported struct tag. Unsupported struct tag: { [value] }.

22NBE

Status description: error: data exception - invalid vector dimensions. Invalid vector dimensions. The number of vector dimensions must be between { [count]1 } and { $count2 }, but is { $count3 }.

22NBF

Status description: error: data exception - property value too big. Property value of type { [typeDescription] } is too big (more than { [bytes] } bytes): { [value] }

22NC1

Status description: error: data exception - graph type element contains duplicated tokens. The graph type element includes a property key with name { [propKey] } more than once.

22NC2

Status description: error: data exception - node element type has no effect. The node element type { [label] } must contain one or more implied labels, or at least one property type.

22NC3

Status description: error: data exception - relationship element type has no effect. The relationship element type { [relType] } must define a source, destination, or at least one property type.

22NC4

Status description: error: data exception - a label cannot be both identifying and implied. The label(s) { [labelList] } are defined as both identifying and implied.

22NC5

Status description: error: data exception - graph type element not found. The { [entityType] } element type referenced by { [graphTypeReference] } does not exist.

22NC6

Status description: error: data exception - independent constraint and node element type have the same label. The independent constraint { [constrDescrOrName] } is using the same label { [label] } as a node element type.

22NC7

Status description: error: data exception - independent constraint and relationship element type have the same relationship type. The independent constraint { [constrDescrOrName] } is using the same relationship type { [relType] } as a relationship element type.

22NC8

Status description: error: data exception - graph type contains duplicated tokens. The graph type includes a label, a relationship type, or an alias with the name { [token] } more than once.

22NC9

Status description: error: data exception - invalid element type constraints in graph type. A { [entityType]1 } element type property { [context] } constraint cannot be specified inline of a { [entityType]2 } element type.

22NCA

Status description: error: data exception - node element type already exists. A node element type identified by the label { [label] } already exists in the graph type.

22NCB

Status description: error: data exception - relationship element type already exists. A relationship element type identified by the relationship type { [relType] } already exists in the graph type.

22NCC

Status description: error: data exception - node element type specified incorrectly. The node element type { [graphTypeElement]1 } identified by the label { [label] } is different to the one specified in the query { [graphTypeElement]2 }.

22NCD

Status description: error: data exception - relationship element type specified incorrectly. The relationship element type { [graphTypeElement]1 } identified by the relationship type { [relType] } is different to the one specified in the query { [graphTypeElement]2 }.

22NCE

Status description: error: data exception - node element type in use. The node element type identified by the label { [label] } is referenced in the graph type element { [graphTypeReference] } and cannot be dropped.

22NCF

Status description: error: data exception - graph type constraint not supported. Graph type constraint definitions are not supported in the { [graphTypeOperation] } operation.

22NCG

Status description: error: data exception - wrong index type. Expected the index { [idx] } to be a { [idxType]1 } index but was a { [idxType]2 } index.

22ND1

Status description: error: data exception - operation not allowed for roles that are granted to an AUTH RULE. Invalid input: '{ [query] }' is not allowed for roles that are granted to an AUTH RULE.

22ND2

Status description: error: data exception - operation not allowed for roles with DENY privileges. Invalid input: '{ [query] }' is not allowed for roles with DENY privileges.

22ND3

Status description: error: data exception - wrong property for vector search with filters. The property { [propKey] } is not an additional property for vector search with filters on the vector index { [idx] } .

Invalid transaction state

Invalid transaction state errors occur when the transaction is in an invalid state, such as when the transaction is terminated or closed, or when there is a conflict between the transaction state and applied updates.

25G02

Status description: error: invalid transaction state - catalog and data statement mixing not supported

25N01

Status description: error: invalid transaction state - invalid combination of statement types. Failed to execute the query { [query] } due to conflicting statement types (read query, write query, schema modification, or administration command). To execute queries in the same transaction, they must be either of the same type, or be a combination of schema modifications and read commands.

25N02

Status description: error: invalid transaction state - unable to complete transaction. Unable to complete transaction. See debug log for details.

25N03

Status description: error: invalid transaction state - concurrent access violation. Transaction is being used concurrently by another request.

25N04

Status description: error: invalid transaction state - specified transaction does not exist. Transaction { [transactionId] } does not exist.

25N05

Status description: error: invalid transaction state - transaction closed. Transaction has been closed.

25N06

Status description: error: invalid transaction state - transaction start failed. Failed to start transaction. See debug log for details.

25N08

Status description: error: invalid transaction state - invalid transaction lease. The lease for the transaction is no longer valid.

25N09

Status description: error: invalid transaction state - internal transaction failure. The transaction failed due to an internal error.

25N11

Status description: error: invalid transaction state - conflicting transaction state. There was a conflict detected between the transaction state and applied updates. Please retry the transaction.

25N12

Status description: error: invalid transaction state - index was dropped. Index { [idx] } was dropped in this transaction and cannot be used.

25N13

Status description: error: invalid transaction state - cannot access entity after removal. A { [entityType] } was accessed after being deleted in this transaction. Verify the transaction statements.

25N14

Status description: error: invalid transaction state - transaction termination client error. The transaction has been terminated. Retry your operation in a new transaction, and you should see a successful result. Reason: { [msg] }

25N15

Status description: error: invalid transaction state - transaction termination database error. The transaction has been terminated. Retry your operation in a new transaction, and you should see a successful result. Reason: { [msg] }

25N16

Status description: error: invalid transaction state - transaction termination transient error. The transaction has been terminated. Retry your operation in a new transaction, and you should see a successful result. Reason: { [msg] }

25N17

Status description: error: invalid transaction state - implicit transaction required. The attempted operation requires an implicit transaction.

Invalid transaction termination

Invalid transaction termination errors occur when the transaction termination fails, such as when the transaction or constituent transaction fails to commit, or when the transaction termination fails to apply or append the transaction.

2DN01

Status description: error: invalid transaction termination - commit failed. Failed to commit transaction.

2DN02

Status description: error: invalid transaction termination - constituent commit failed. Failed to commit constituent transaction. See debug log for details.

2DN03

Status description: error: invalid transaction termination - transaction termination failed. Failed to terminate transaction. See debug log for details.

2DN04

Status description: error: invalid transaction termination - constituent transaction termination failed. Failed to terminate constituent transaction. See debug log for details.

2DN05

Status description: error: invalid transaction termination - failed to apply transaction. There was an error on applying the transaction. See logs for more information.

2DN06

Status description: error: invalid transaction termination - failed to append transaction. There was an error on appending the transaction. See logs for more information.

2DN07

Status description: error: invalid transaction termination - inner transactions still open. Unable to commit transaction because it still have non-closed inner transactions.

Transaction rollback

Transaction rollback errors occur when there is a failure in a transaction or a constituent transaction rollback.

40000

Status description: error: transaction rollback

40003

Status description: error: transaction rollback - statement completion unknown

40N01

Status description: error: transaction rollback - rollback failed. Failed to rollback transaction. See debug log for details.

40N02

Status description: error: transaction rollback - constituent rollback failed. Failed to rollback constituent transaction. See debug log for details.

Syntax error or access rule violation

Syntax error or access rule violation errors occur when a Cypher query contains invalid syntax or when a client request violates the access rules, such as when a query tries to access a database without enough privileges, etc.

42000

Status description: error: syntax error or access rule violation

42001

Status description: error: syntax error or access rule violation - invalid syntax

42006

Status description: error: syntax error or access rule violation - number of edge labels below supported minimum

42007

Status description: error: syntax error or access rule violation - number of edge labels exceeds supported maximum

42008

Status description: error: syntax error or access rule violation - number of edge properties exceeds supported maximum

42009

Status description: error: syntax error or access rule violation - number of node labels below supported minimum

42010

Status description: error: syntax error or access rule violation - number of node labels exceeds supported maximum

42011

Status description: error: syntax error or access rule violation - number of node properties exceeds supported maximum

42012

Status description: error: syntax error or access rule violation - number of node type key labels below supported minimum

42013

Status description: error: syntax error or access rule violation - number of node type key labels exceeds supported maximum

42014

Status description: error: syntax error or access rule violation - number of edge type key labels below supported minimum

42015

Status description: error: syntax error or access rule violation - number of edge type key labels exceeds supported maximum

42I00

Status description: error: syntax error or access rule violation - invalid case expression. CASE expressions must have the same number of WHEN and THEN operands.

42I01

Status description: error: syntax error or access rule violation - invalid FOREACH. Invalid use of { [clause] } inside FOREACH.

42I02

Status description: error: syntax error or access rule violation - invalid comment. Failed to parse comment. A comment starting with /* must also have a closing */.

42I04

Status description: error: syntax error or access rule violation - invalid expression. { [expr] } cannot be used in a { [clause] } clause.

42I05

Status description: error: syntax error or access rule violation - invalid FIELDTERMINATOR. The FIELDTERMINATOR specified for LOAD CSV can only be one character wide.

42I06

Status description: error: syntax error or access rule violation - invalid input. Invalid input { [input] }, expected: { [valueList] }.

42I07

Status description: error: syntax error or access rule violation - invalid integer literal. The given { [valueType] } literal { [input] } is invalid.

42I08

Status description: error: syntax error or access rule violation - invalid lower bound. The lower bound of the variable length relationship used in the { [fun] } function must be 0 or 1.

42I10

Status description: error: syntax error or access rule violation - invalid label expression. Mixing label expression symbols (|, &, !, and %) with colon (:) between labels is not allowed. This expression could be expressed as { [syntax] }.

42I11

Status description: error: syntax error or access rule violation - invalid name. A { [tokenType] } name cannot be empty or contain any null-bytes: { [input] }.

42I12

Status description: error: syntax error or access rule violation - invalid nesting of quantified path patterns. Quantified path patterns cannot be nested.

42I13

Status description: error: syntax error or access rule violation - invalid number of procedure or function arguments. The procedure or function call does not provide the required number of arguments; expected { [count]1 } but got { $count2 }. The procedure or function { [procFun] } has the signature: { [sig] }.

42I14

Status description: error: syntax error or access rule violation - invalid number of relationship types. Exactly one relationship type must be specified for { [variable] }.

42I15

Status description: error: syntax error or access rule violation - invalid number of statements. Expected exactly one statement per query but got: { [count] }.

42I16

Status description: error: syntax error or access rule violation - invalid point. Map with keys { [mapKeyList] } is not a valid POINT. Use either Cartesian or geographic coordinates.

42I17

Status description: error: syntax error or access rule violation - invalid quantifier. A quantifier must not have a lower bound greater than the upper bound.

42I18

Status description: error: syntax error or access rule violation - invalid reference to implicitly grouped expressions. The aggregation column contains implicit grouping expressions referenced by the variables { [variableList] }. Implicit grouping expressions are variables not explicitly declared as grouping keys.

42I19

Status description: error: syntax error or access rule violation - invalid string literal. Failed to parse string literal. The query must contain an even number of non-escaped quotes.

42I20

Status description: error: syntax error or access rule violation - invalid symbol in expression. Label expressions and relationship type expressions cannot contain { [input] }. To express a label disjunction use { [labelExpr] } instead.

42I21

Status description: error: syntax error or access rule violation - invalid reference to variable out of scope. Not allowed to reference { [variableList] } from within a parenthesized/quantified path pattern like { [pat] } in the same graph pattern.

42I23

Status description: error: syntax error or access rule violation - invalid quantified path pattern in shortest path. The { [fun] } function cannot contain a quantified path pattern.

42I24

Status description: error: syntax error or access rule violation - invalid use of aggregate function. Aggregate expression { [expr] } is not allowed in this context.

42I25

Status description: error: syntax error or access rule violation - invalid use of CALL IN TRANSACTIONS. CALL { … } IN TRANSACTIONS is not supported after a write clause.

42I26

Status description: error: syntax error or access rule violation - invalid DELETE. DELETE … does not support removing labels from a node. Use REMOVE … instead.

42I27

Status description: error: syntax error or access rule violation - invalid use of DISTINCT with non-aggregate function. DISTINCT cannot be used with the { [fun] } function.

42I28

Status description: error: syntax error or access rule violation - invalid use of importing WITH. Importing WITH can consist only of direct references to outside variables. { [input] } is not allowed.

42I29

Status description: error: syntax error or access rule violation - invalid use of IS. The IS keyword cannot be used together with multiple labels in { [input] }. Rewrite the expression as { [replacement] }.

42I30

Status description: error: syntax error or access rule violation - invalid use of label expressions. Label expressions cannot be used in { [expr] }.

42I31

Status description: error: syntax error or access rule violation - invalid use of MATCH. MATCH … cannot directly follow an OPTIONAL MATCH …. Use a WITH clause between them.

42I32

Status description: error: syntax error or access rule violation - invalid use of node and relationship pattern predicate. Node and relationship pattern predicates cannot be used in { [context] }. They can only be used in a MATCH clause or inside a pattern comprehension.

42I33

Status description: error: syntax error or access rule violation - invalid use of NOT NULL. Closed Dynamic Union types cannot be appended with NOT NULL, specify NOT NULL on inner types instead.

42I34

Status description: error: syntax error or access rule violation - invalid use of pattern expression. A pattern expression can only be used to test the existence of a pattern. Use a pattern comprehension instead.

42I35

Status description: error: syntax error or access rule violation - invalid use of relationship type expression. Relationship type expressions can only be used in MATCH ….

42I36

Status description: error: syntax error or access rule violation - invalid use of REPORT STATUS. REPORT STATUS can only be used when specifying ON ERROR CONTINUE or ON ERROR BREAK.

42I37

Status description: error: syntax error or access rule violation - invalid use of RETURN *. RETURN * is not allowed when there are no variables in scope.

42I38

Status description: error: syntax error or access rule violation - invalid use of RETURN. RETURN … can only be used at the end of a query or subquery.

42I39

Status description: error: syntax error or access rule violation - invalid use of shortest path function. Mixing the { [fun] } function with path selectors, explicit match modes, or explicit path modes is not allowed.

42I40

Status description: error: syntax error or access rule violation - invalid use of UNION and UNION ALL. UNION and UNION ALL cannot be combined.

42I41

Status description: error: syntax error or access rule violation - invalid use of variable length relationship. Variable length relationships cannot be used in { [value] }.

42I42

Status description: error: syntax error or access rule violation - invalid use of YIELD. Cannot use YIELD on a call to a void procedure.

42I43

Status description: error: syntax error or access rule violation - invalid use of YIELD *. YIELD * can only be used with a standalone procedure call.

42I45

Status description: error: syntax error or access rule violation - invalid use of multiple path patterns. Multiple path patterns cannot be used in the same clause in combination with a selective path selector. { [action] }

42I46

Status description: error: syntax error or access rule violation - invalid use of a node pattern pair. Node pattern pairs are only supported for quantified path patterns.

42I47

Status description: error: syntax error or access rule violation - parser error. Parser Error: { [msg] }.

42I48

Status description: error: syntax error or access rule violation - invalid use of a subquery in MERGE. Subqueries are not allowed in a MERGE clause.

42I49

Status description: error: syntax error or access rule violation - invalid inequality operator. Unknown inequality operator !=. The operator for inequality in Cypher is <>.

42I50

Status description: error: syntax error or access rule violation - token name too long. Invalid input { [input] }... A { [tokenType] } name cannot be longer than { [value] }.

42I51

Status description: info: invalid call signature. The procedure or function { [procFun] } must have the signature: { [sig] }.

42I52

Status description: error: syntax error or access rule violation - no longer valid syntax. { [msg] }

42I53

Status description: error: syntax error or access rule violation - unsupported coordinate type. Unknown coordinate type: { [input] }.

42I54

Status description: error: syntax error or access rule violation - invalid use of INSERT. { [cause] } is not allowed in INSERT. Use CREATE or { [replacement] }.

42I55

Status description: error: syntax error or access rule violation - invalid use of dynamic label or type. Dynamic { [tokenType] } using $any() are not allowed in { [clause] }.

42I56

Status description: error: syntax error or access rule violation - invalid relationship direction. Only directed relationships are supported in { [clause]}.

42I57

Status description: error: syntax error or access rule violation - invalid query ending. {[exprType]} cannot contain a query ending with {[clause]}.

42I58

Status description: error: syntax error or access rule violation - invalid entity reference. Entity, {[expr]}, cannot be created and referenced in the same clause.

42I59

Status description: error: syntax error or access rule violation - dynamic entity type not allowed. Dynamic label and types are only allowed in { [clauseList] } clauses.

42I60

Status description: error: syntax error or access rule violation - invalid glob escaping. Each part of the glob (a block of text up until a dot) must either be fully escaped or not escaped at all.

42I61

Status description: error: syntax error or access rule violation - missing LOOKUP INDEX function name. Missing function name for the LOOKUP INDEX.

42I62

Status description: error: syntax error or access rule violation - unsupported distance metric. Unknown distance metric: { [input] }.

42I63

Status description: error: syntax error or access rule violation - wrong subclause order. ORDER BY, { [clause] } and LIMIT can only be used in this order in RETURN.

42I64

Status description: error: syntax error or access rule violation - unsupported operation. { [msg] } currently not supported after NEXT { [context] }.

42I65

Status description: error: syntax error or access rule violation - invalid pattern character. An invalid character is used in the pattern. Verify that all characters are supported by { [valueType] }.

42I66

Status description: error: syntax error or access rule violation - pattern parsing failed. Pattern parsing failed. Make sure that an even number of escapes are used in the pattern.

42I67

Status description: error: syntax error or access rule violation - unsupported language feature. The query is parsable in CYPHER { [version]2 }, but it is run in CYPHER { [version]1 }. Consider changing the database default Cypher version using ALTER DATABASE SET DEFAULT LANGUAGE or prefix the query with CYPHER { [feat]2 }.

42I68

Status description: error: syntax error or access rule violation - mismatched pattern. Pattern, { [input]1 }, does not match input, { [input]2 }. Verify that the pattern is valid for constructing { [valueType] }.

42I69

Status description: error: syntax error or access rule violation - invalid search variable reference. { [variable] } must reference a variable from the same MATCH statement.

42I70

Status description: error: syntax error or access rule violation - search clause with multiple bound variables. In order to have a search clause, a MATCH statement can only have one bound variable.

42I71

Status description: error: syntax error or access rule violation - search clause with invalid predicates. In order to have a search clause, a MATCH statement can only have predicates on the bound node or relationship.

42I72

Status description: error: syntax error or access rule violation - search clause with too complex pattern. In order to have a search clause, a MATCH statement can only have a single node or relationship pattern and no selectors.

42I73

Status description: error: syntax error or access rule violation - invalid predicate for vector search with filters. The vector search filter predicate { [expr] } must consist of one or more property predicates joined by AND, and the combined property predicates for each property must specify either an exact value (e.g. x.prop = 1), a half-bounded range (e.g. x.prop >= 1), or a bounded range (e.g. x.prop > 1 AND x.prop < 100).

42I74

Status description: error: syntax error or access rule violation - wrong variable for vector search with filters. The variable { [variable]1 } in a vector search filter property predicate must be the same as the search clause binding variable { [variable]2 }.

42I75

Status description: error: syntax error or access rule violation - self-referencing in vector search. The expression { [expr] } in the search clause may not depend on the search clause binding variable { [variable] }.

42I76

Status description: error: syntax error or access rule violation - index or constraint value too long. The provided index or constraint { [item] } { [input] } ({ [bytes]1 } bytes) exceeded limit of { [bytes]2 } bytes.

42N00

Status description: error: syntax error or access rule violation - graph reference not found. A graph reference with the name { [db] } was not found. Verify that the spelling is correct.

42N01

Status description: error: syntax error or access rule violation - no such constituent graph exists in composite database. The constituent graph { [graph] } was not found in the in composite database { [db] }. Verify that the spelling is correct.

42N02

Status description: error: syntax error or access rule violation - writing in read access mode. Writing in read access mode not allowed.

42N03

Status description: error: syntax error or access rule violation - writing to multiple graphs. Writing to multiple graphs in the same transaction is not allowed. Use CALL IN TRANSACTION or create separate transactions in your application.

42N04

Status description: error: syntax error or access rule violation - unsupported access of composite database. Failed to access database identified by { [db]1 } while connected to session database { $db2 }. Connect to { $db3 } directly.

42N05

Status description: error: syntax error or access rule violation - unsupported access of standard database. Failed to access database identified by { [db]1 } while connected to composite session database { $db2 }. Connect to { $db3 } directly or create an alias in the composite database.

42N06

Status description: error: syntax error or access rule violation - unsupported action on composite database. { [action] } is not supported on composite databases.

42N07

Status description: error: syntax error or access rule violation - variable shadowing. The variable { [variable] } is shadowing a variable with the same name from the outer scope and needs to be renamed.

42N08

Status description: error: syntax error or access rule violation - no such procedure. The procedure { [procFun] } was not found. Verify that the spelling is correct.

42N09

Status description: error: syntax error or access rule violation - no such user. A user with the name { [user] } was not found. Verify that the spelling is correct.

42N0A

Status description: error: syntax error or access rule violation - invalid shard target. { [action] } is not allowed with a shard target. Connect to { [db]1 } in order to read or write data from { db2 }.

42N0B

Status description: error: syntax error or access rule violation - cannot replace sharded database. The database identified by { [db]1 } is sharded. Drop the database { [db]2 } before recreating.

42N0D

Status description: error: syntax error or access rule violation - cannot call function from this context. The function { [fun] } cannot be called from the current context. It can only be used { [context] }.

42N0E

Status description: error: syntax error or access rule violation - cannot call function without metadata. The function { [fun] } cannot be called without metadata.

42N0F

Status description: error: syntax error or access rule violation - cannot call function without metadata for realm. The function { [fun] } cannot be called without metadata for realm: { [auth] }.

42N10

Status description: error: syntax error or access rule violation - no such role. A role with the name { [role] } was not found. Verify that the spelling is correct.

42N11

Status description: error: syntax error or access rule violation - graph reference already exists. A graph reference with the name { [dbList] } already exists.

42N12

Status description: error: syntax error or access rule violation - user already exists. A user with the name { [user] } already exists.

42N13

Status description: error: syntax error or access rule violation - role already exists. A role with the name { [role] } already exists.

42N14

Status description: error: syntax error or access rule violation - invalid use of command. { [clause] } cannot be used together with { [cmd] }.

42N15

Status description: error: syntax error or access rule violation - invalid use of reserved keyword. { [syntax] } is a reserved keyword and cannot be used in this place.

42N16

Status description: error: syntax error or access rule violation - unsupported index or constraint. Only single property { [idxType] } are supported.

42N17

Status description: error: syntax error or access rule violation - unsupported request. { [input] } is not allowed on the system database.

42N18

Status description: error: syntax error or access rule violation - read-only database. The database is in read-only mode.

42N19

Status description: error: syntax error or access rule violation - duplicate clause. Duplicate { [syntax] } clause.

42N20

Status description: error: syntax error or access rule violation - empty list range operator. The list range operator [ ] cannot be empty.

42N21

Status description: error: syntax error or access rule violation - unaliased return item. Expression in { [clause] } must be aliased (use AS).

42N22

Status description: error: syntax error or access rule violation - single return column required. A COLLECT subquery must end with a single return column.

42N23

Status description: error: syntax error or access rule violation - missing reference to aggregation function. The aggregating function must be included in the { [clause] } clause for use in ORDER BY ….

42N24

Status description: error: syntax error or access rule violation - missing WITH. A WITH clause is required between { [input]1 } and { $input2 }.

42N25

Status description: error: syntax error or access rule violation - missing YIELD. Procedure call inside a query does not support naming results implicitly. Use YIELD instead.

42N26

Status description: error: syntax error or access rule violation - multiple join hints on same variable. Multiple join hints for the same variable { [variable] } are not supported.

42N28

Status description: error: syntax error or access rule violation - patterns or variables not statically inferrable. Only statically inferrable patterns and variables are allowed in { [input] }.

42N29

Status description: error: syntax error or access rule violation - unbound variables in pattern expression. Pattern expressions are not allowed to introduce new variables: { [variable] }.

42N31

Status description: error: syntax error or access rule violation - specified number out of range. Expected { [component] } to be { [valueType] } in the range { [lower] } to { [upper] } but found { [value] }.

42N32

Status description: error: syntax error or access rule violation - invalid use of parameter map. Parameter maps cannot be used in { [keyword] } patterns. Use a literal map instead.

42N34

Status description: error: syntax error or access rule violation - path bound in quantified path pattern. Path cannot be bound in a quantified path pattern.

42N35

Status description: error: syntax error or access rule violation - unsupported path selector in path pattern. The path selector { [selector] } is not supported within quantified or parenthesized path patterns.

42N36

Status description: error: syntax error or access rule violation - procedure call without parentheses. Procedure call is missing parentheses.

42N37

Status description: error: syntax error or access rule violation - invalid use of relationship pattern predicates in variable length relationships. Relationship pattern predicates cannot be use in variable length relationships.

42N38

Status description: error: syntax error or access rule violation - duplicate return item name. Return items must have unique names.

42N39

Status description: error: syntax error or access rule violation - incompatible return column names. All { [context] } must have the same return column names. Use AS to ensure columns have the same name.

42N3A

Status description: error: syntax error or access rule violation - incompatible conditional query. All { [context] } need to either return rows or update the graph.

42N3B

Status description: error: syntax error or access rule violation - incompatible number of return columns. All { [context] } must return the same number of columns.

42N3C

Status description: error: syntax error or access rule violation - invalid use of CALL { … }. Not possible to enclose { [clause] } in CALL { … }. Use CALL () { … } instead.

42N40

Status description: error: syntax error or access rule violation - single relationship pattern required. The { [fun] } function must contain one relationship pattern.

42N41

Status description: error: syntax error or access rule violation - missing |-expression. The reduce function requires a | expression after the accumulator.

42N42

Status description: error: syntax error or access rule violation - unsupported sub-path binding. Sub-path assignment is not supported.

42N44

Status description: error: syntax error or access rule violation - inaccessible variable. It is not possible to access the variable { [variable] } declared before the { [clause] } clause when using DISTINCT or an aggregation.

42N45

Status description: error: syntax error or access rule violation - unexpected end of input. Unexpected end of input, expected CYPHER, EXPLAIN, PROFILE or a query.

42N47

Status description: error: syntax error or access rule violation - invalid use of UNION and CALL IN TRANSACTIONS. CALL { … } IN TRANSACTIONS is not supported in … UNION ….

42N48

Status description: error: syntax error or access rule violation - no such function. The function { [fun] } was not found. Verify that the spelling is correct.

42N49

Status description: error: syntax error or access rule violation - unsupported normal form. Unknown Normal Form: { [input] }.

42N50

Status description: error: syntax error or access rule violation - procedure return column not defined. The procedure return column { [variable] } is not defined for this procedure. Verify that the spelling is correct.

42N51

Status description: error: syntax error or access rule violation - invalid parameter. Invalid parameter { [param] }.

42N52

Status description: error: syntax error or access rule violation - invalid value type. { [input] } is not a recognized Cypher type.

42N53

Status description: error: syntax error or access rule violation - unsafe usage of repeatable elements. The quantified path pattern may yield an infinite number of rows under match mode REPEATABLE ELEMENTS. Add an upper bound to the quantified path pattern.

42N54

Status description: error: syntax error or access rule violation - unsupported match mode. The match mode { [matchMode] } is not supported.

42N56

Status description: error: syntax error or access rule violation - unsupported use of properties. Properties are not supported in the { [fun] } function.

42N57

Status description: error: syntax error or access rule violation - invalid use of data-modifications in expressions. { [expr] } cannot contain any updating clauses.

42N58

Status description: error: syntax error or access rule violation - unsupported use of nesting. Nested CALL { … } IN TRANSACTIONS is not supported.

42N59

Status description: error: syntax error or access rule violation - variable already defined. Variable { [variable] } already declared.

42N60

Status description: error: syntax error or access rule violation - unsupported combination of match mode and path mode. REPEATABLE ELEMENTS with { [pathMode] } path mode is not supported.

42N61

Status description: error: syntax error or access rule violation - unsupported mixing of different path modes. Mixing { [pathModeList] } in the same graph pattern is not supported. Split the pattern into separate MATCH clauses instead.

42N62

Status description: error: syntax error or access rule violation - variable not defined. Variable { [variable] } not defined.

42N63

Status description: error: syntax error or access rule violation - inner type with different nullability. All inner types in a Closed Dynamic Union must be nullable, or be appended with NOT NULL.

42N64

Status description: error: syntax error or access rule violation - at least one node or relationship required. A quantified or parenthesized path pattern must have at least one node or relationship pattern.

42N65

Status description: error: syntax error or access rule violation - node variable not bound. The { [fun] } function requires bound node variables when it is not part of a MATCH ….

42N66

Status description: error: syntax error or access rule violation - relationship variable already bound. Bound relationships are not allowed in calls to the { [fun] } function.

42N68

Status description: error: syntax error or access rule violation - duplicate variable definition. Variables cannot be defined more than once in a { [clause] } clause.

42N69

Status description: error: syntax error or access rule violation - function not allowed inside expression. The { [fun] } function is only allowed as a top-level element and not inside an { [expr] }.

42N70

Status description: error: syntax error or access rule violation - function without required WHERE clause. The function { [fun] } requires a WHERE clause.

42N71

Status description: error: syntax error or access rule violation - incomplete query. A query must conclude with a RETURN clause, a FINISH clause, an update clause, a unit subquery call, or a procedure call without a YIELD clause.

42N72

Status description: error: syntax error or access rule violation - graph function only supported on composite databases. Calling graph functions is only supported on composite databases. Use the name directly or connect to a composite database with the desired constituents.

42N73

Status description: error: syntax error or access rule violation - invalid placement of USE clause. The USE clause must be the first clause of a query or an operand to … UNION … . In a CALL sub-query, it can also be the second clause if the first clause is an importing WITH.

42N74

Status description: error: syntax error or access rule violation - invalid nested USE clause. Failed to access { [db]1 } and { $db2 }. Child USE clauses must target the same graph as their parent query. Run in separate (sub)queries instead.

42N75

Status description: error: syntax error or access rule violation - invalid use of graph function. A call to the graph function { [fun] } is only allowed as the top-level argument of a USE clause.

42N76

Status description: error: syntax error or access rule violation - unfulfillable hints. The hint(s) { [hintList] } cannot be fulfilled.

42N77

Status description: error: syntax error or access rule violation - missing hint predicate. The hint { [hint] } cannot be fulfilled. The query does not contain a compatible predicate for { [entityType] } on { [variable] }.

42N78

Status description: error: syntax error or access rule violation - variable already bound. Node { [variable] } has already been bound and cannot be modified by the { [clause] } clause.

42N79

Status description: error: syntax error or access rule violation - invalid USE clause. The USE clause is not required for administration commands. Retry the query without the USE clause, and it will be routed automatically.

42N81

Status description: error: syntax error or access rule violation - missing request parameter. Expected { [param] }, but got { [paramList] }.

42N82

Status description: error: syntax error or access rule violation - cannot drop database with aliases. The database identified by { [db] } has one or more aliases. Drop the aliases { [aliasList] } before dropping the database.

42N83

Status description: error: syntax error or access rule violation - impersonation disallowed while password change required. Cannot impersonate a user while password change required.

42N84

Status description: error: syntax error or access rule violation - TERMINATE TRANSACTION misses YIELD clause. WHERE clause without YIELD clause. Use TERMINATE TRANSACTION … YIELD … WHERE ….

42N85

Status description: error: syntax error or access rule violation - cannot specify both allowed and denied databases. Allowed and denied database options are mutually exclusive.

42N86

Status description: error: syntax error or access rule violation - wildcard in parameter. { [syntax] } failed. Parameterized database and graph names do not support wildcards.

42N87

Status description: error: syntax error or access rule violation - database or alias with similar name exists. The database or alias name { [db]1 } conflicts with the name { [db]2 } of an existing database or alias.

42N88

Status description: error: syntax error or access rule violation - cannot grant privilege. Permission cannot be granted for REMOVE IMMUTABLE PRIVILEGE.

42N89

Status description: error: syntax error or access rule violation - invalid driver settings map. Failed evaluating the given driver settings. { [cause] }

42N90

Status description: error: syntax error or access rule violation - cannot alter immutable composite database. Composite databases cannot be altered (database: { [db] }).

42N92

Status description: error: syntax error or access rule violation - cannot combine old and new auth provider syntax. Cannot combine old and new auth syntax for the same auth provider.

42N94

Status description: error: syntax error or access rule violation - incomplete ALTER USER command. 'ALTER USER' requires at least one clause.

42N95

Status description: error: syntax error or access rule violation - provider-id combination already exists. The combination of provider and id is already in use.

42N96

Status description: error: syntax error or access rule violation - invalid user configuration. User has no auth provider. Add at least one auth provider for the user or consider suspending them.

42N97

Status description: error: syntax error or access rule violation - missing mandatory auth clause. Clause { [clause] } is mandatory for auth provider { [auth] }.

42N98

Status description: error: syntax error or access rule violation - cannot modify own user. Cannot modify the user record of the current user.

42N99

Status description: error: syntax error or access rule violation - cannot delete own user. Cannot delete the user record of the current user.

42NA0

Status description: error: syntax error or access rule violation - operations must be executed on constituent. Query contains operations that must be executed on the constituent.

42NA1

Status description: error: syntax error or access rule violation - graph access operations on composite database. Graph access operations are not supported on composite databases.

42NA2

Status description: error: syntax error or access rule violation - database operations on composite database. Database operations are not supported on composite databases.

42NA3

Status description: error: syntax error or access rule violation - schema operations on composite database. Schema operations are not supported on composite databases.

42NA4

Status description: error: syntax error or access rule violation - transaction operations on composite database. Transaction operations are not supported on composite databases.

42NA5

Status description: error: syntax error or access rule violation - accessing multiple graphs only supported on composite databases. Accessing multiple graphs in the same query is only supported on composite databases. Connect to a composite database with the desired constituents.

42NA6

Status description: error: syntax error or access rule violation - invalid alias target. Aliases are not allowed to target composite databases.

42NA7

Status description: error: syntax error or access rule violation - referenced database not found. No database is corresponding to { [db] }. Verify that the elementId is correct.

42NA8

Status description: error: syntax error or access rule violation - invalid reference in command. Invalid reference in command { [cmd] }.

42NA9

Status description: error: syntax error or access rule violation - system database procedure rules. The system database supports a restricted set of Cypher clauses. The supported clause structure for procedure calls is: CALL, YIELD, RETURN. YIELD and RETURN clauses are optional. The order of the clauses is fixed and each can only occur once.

42NAA

Status description: error: syntax error or access rule violation - incorrectly formatted graph reference. Incorrectly formatted graph reference { [input] }. Expected a single quoted or unquoted identifier. Separate name parts should not be quoted individually.

42NAB

Status description: error: syntax error or access rule violation - not supported standalone call. WHERE is not supported in a standalone call. Use CALL … YIELD … WHERE … RETURN … instead.

42NAC

Status description: error: syntax error or access rule violation - invalid CREATE DATABASE statement. The backup metadata script contains an invalid or missing CREATE DATABASE statement. The metadata script must contain exactly one CREATE DATABASE statement and it must use the parameter $database.

42NAD

Status description: error: syntax error or access rule violation - no such auth rule. An auth rule with the name { [authRule] } was not found. Verify that the spelling is correct.

42NAE

Status description: error: syntax error or access rule violation - auth rule already exists. An auth rule with the name { [authRule] } already exists.

42NFC

Status description: error: syntax error or access rule violation - auth info validation error. Authentication and/or authorization could not be validated. See security logs for details.

42NFD

Status description: error: syntax error or access rule violation - credentials expired. Permission denied. The credentials you provided were valid, but must be changed before you can use this instance.

42NFE

Status description: error: syntax error or access rule violation - auth info expired. Authentication and/or authorization info expired.

42NFF

Status description: error: syntax error or access rule violation - permission/access denied. Access denied, see the security logs for details.

General processing exceptions

General processing exceptions occur when there is a general processing error, such as an internal error, deadlock, execution failure, invalid server state transition, constraint creation or drop failure, etc.

50N00

Status description: error: general processing exception - internal error. Internal exception raised { [msgTitle] }: { [msg] }

50N05

Status description: error: general processing exception - deadlock detected. Deadlock detected while trying to acquire locks. See log for more details.

50N06

Status description: error: general processing exception - remote execution client error. Remote execution failed. See cause for more details.

50N07

Status description: error: general processing exception - execution failed. Execution failed. See cause and debug log for details.

50N09

Status description: error: general processing exception - invalid server state transition. The server transitioned into a server state that is not valid in the current context: { [boltServerState] }.

50N10

Status description: error: general processing exception - index drop failed. Unable to drop { [idxDescrOrName] }.

50N11

Status description: error: general processing exception - constraint creation failed. Unable to create { [constrDescrOrName] }.

50N12

Status description: error: general processing exception - constraint drop failed. Unable to drop { [constrDescrOrName] }.

50N13

Status description: error: general processing exception - constraint validation error. Unable to validate constraint { [constrDescrOrName] }.

50N14

Status description: error: general processing exception - constraint violation. A constraint imposed by the database was violated.

50N15

Status description: error: general processing exception - unsupported index operation. The system attemped to execute an unsupported operation on index { [idx] }. See debug.log for more information.

50N16

Status description: error: general processing exception - remote execution transient error. Remote execution failed. See cause for more details.

50N17

Status description: error: general processing exception - remote execution database error. Remote execution failed. See cause for more details.

50N18

Status description: error: general processing exception - shard execution transient error. Communication with shard { [graph] } failed. See cause for more details.

50N19

Status description: error: general processing exception - shard execution database error. Communication with shard { [graph] } failed. See cause for more details.

50N20

Status description: error: general processing exception - shard execution client error. Communication with shard { [graph] } failed. See cause for more details.

50N21

Status description: error: general processing exception - no such schema descriptor. The { [schemaDescrType] } was not found for { [schemaDescr] }. Verify that the spelling is correct.

50N23

Status description: error: general processing exception - transaction retry aborted. Transaction retry aborted after { [count] } attempts. Retry timed out with a maximum retry duration of { [timeAmount] } { [timeUnit] }.

50N24

Status description: error: general processing exception - sharded properties transaction handling database error. Unexpected exception while getting transaction state.

50N25

Status description: error: general processing exception - sharded properties transaction handling client error. Unexpected exception while getting transaction state.

50N26

Status description: error: general processing exception - invalid backup metadata script. The backup metadata script contains invalid syntax.

50N42

Status description: error: general processing exception - unexpected error. Unexpected error has occurred. See debug log for details.

System configuration or operation exceptions

System configuration or operation exception errors occur when there is an error in the system configuration or operation, such as procedure registration failure, a missing class field annotation, an unsupported injectable component type, duplicate field names, invalid map key type, etc.

51N00

Status description: error: system configuration or operation exception - procedure registration error. Failed to register procedure/function.

51N01

Status description: error: system configuration or operation exception - class field annotation should be public, non-final, and non-static. The field { [procField] } in the class { [procClass] } is annotated as a @Context field, but it is declared as static. @Context fields must be public, non-final and non-static.

51N02

Status description: error: system configuration or operation exception - unsupported injectable component type. Unable to set up injection for procedure { [procClass] }. The field { [procField] } has type { [procFieldType] } which is not a supported injectable component.

51N03

Status description: error: system configuration or operation exception - unable to access field. Unable to set up injection for { [procClass] }, failed to access field { [procField] }.

51N04

Status description: error: system configuration or operation exception - missing class field annotation. The field { [procField] } on { [procClass] } must be annotated as a @Context field in order to store its state.

51N05

Status description: error: system configuration or operation exception - class field should be public and non-final. The field { [procField] } on { [procClass] } must be declared non-final and public.

51N06

Status description: error: system configuration or operation exception - missing argument name. The argument at position { [pos] } in { [procMethod] } requires a @Name annotation and a non-empty name.

51N07

Status description: error: system configuration or operation exception - invalid ordering of default arguments. The { [procFun] } contains a non-default argument after a default argument. Non-default arguments are not allowed to be positioned after default arguments.

51N08

Status description: error: system configuration or operation exception - exactly one @UserAggregationResult method and one @UserAggregationUpdate method required. The class { [procClass] } must contain exactly one @UserAggregationResult method and exactly one @UserAggregationUpdate method.

51N09

Status description: error: system configuration or operation exception - @UserAggregationUpdate method must be public and void. The @UserAggregationUpdate method { [procMethod] } of { [procClass] } must be public and have the return type void.

51N10

Status description: error: system configuration or operation exception - aggregation method not public. The method { [procMethod] } of { [procClass] } must be public.

51N11

Status description: error: system configuration or operation exception - class not public. The class { [procClass] } must be public.

51N12

Status description: error: system configuration or operation exception - class not void. The procedure { [proc] } has zero return columns and must be defined as void.

51N13

Status description: error: system configuration or operation exception - procedure or function name already in use. Unable to register the procedure or function { [procFun] } because the name is already in use.

51N14

Status description: error: system configuration or operation exception - duplicate field name. The procedure { [proc] } has a duplicate { [procFieldType] } field, { [procField] }.

51N15

Status description: error: system configuration or operation exception - invalid map key type. Type mismatch for map key. Required STRING, but found { [valueType] }.

51N16

Status description: error: system configuration or operation exception - invalid default value type. Type mismatch for the default value. Required { [valueType] }, but found { [input] }.

51N17

Status description: error: system configuration or operation exception - invalid procedure or function name. Procedures and functions cannot be defined in the root namespace, or use a reserved namespace. Use the package name instead (e.g., org.example.com.{ [procFun] })`.

51N18

Status description: error: system configuration or operation exception - invalid method return type. The method { [procMethod] } has an invalid return type. Procedures must return a stream of records, where each record is of a defined concrete class.

51N20

Status description: error: system configuration or operation exception - cannot inject field. The field { [procField] } is not injectable. Ensure the field is marked as public and non-final.

51N21

Status description: error: system configuration or operation exception - procedure registry is busy. The procedure registration failed because the procedure registry was busy. Try again.

51N22

Status description: error: system configuration or operation exception - exhaustive shortest path search disabled. Finding the shortest path for the given pattern requires an exhaustive search. To enable exhaustive searches, set cypher.forbid_exhaustive_shortestpath to false.

51N23

Status description: error: system configuration or operation exception - cyclic shortest path search disabled. Cannot find the shortest path when the start and end nodes are the same. To enable this behavior, set dbms.cypher.forbid_shortestpath_common_nodes to false.

51N24

Status description: error: system configuration or operation exception - insufficient resources for plan search. Could not find a query plan within given time and space limits.

51N25

Status description: error: system configuration or operation exception - database is busy. Cannot compile query due to excessive updates to indexes and constraints.

51N26

Status description: error: system configuration or operation exception - not supported in this version. { [item] } is not available. This implementation of Cypher does not support { [feat] }.

51N27

Status description: error: system configuration or operation exception - not supported in this edition. { [feat] } is not supported in { [edition] }.

51N28

Status description: error: system configuration or operation exception - not supported by this database. This Cypher command must be executed against the database { [db] }.

51N29

Status description: error: system configuration or operation exception - not supported by this server. The command { [cmd] } must be executed on the current LEADER server.

51N2A

Status description: error: system configuration or operation exception - not supported with auth disabled. The command { [cmd] } is not available with auth disabled.

51N30

Status description: error: system configuration or operation exception - not supported with this configuration. { [item] } is not supported in { [context] }.

51N31

Status description: error: system configuration or operation exception - not supported. { [feat] } is not supported in { [context] }.

51N32

Status description: error: system configuration or operation exception - server panic. Server is in panic.

51N33

Status description: error: system configuration or operation exception - replication error. This member failed to replicate transaction, try again.

51N34

Status description: error: system configuration or operation exception - write transaction failed due to leader change. Failed to write to the database due to a cluster leader change. Retrying your request at a later time may succeed.

51N35

Status description: error: system configuration or operation exception - database location changed. The location of { [db] } has changed while the transaction was running.

51N36

Status description: error: system configuration or operation exception - out of memory. There is not enough memory to perform the current task.

51N37

Status description: error: system configuration or operation exception - stack overflow. There is not enough stack size to perform the current task.

51N38

Status description: error: system configuration or operation exception - failed to acquire execution thread. There are insufficient threads available for executing the current task.

51N39

Status description: error: system configuration or operation exception - raft log corrupted. Expected set of files not found on disk. Please restore from backup.

51N40

Status description: error: system configuration or operation exception - unable to start database. Database { [db] } failed to start. Try restarting it.

51N41

Status description: error: system configuration or operation exception - admin operation failed. Server or database admin operation not possible. Reason: { [msg] }

51N43

Status description: error: system configuration or operation exception - cannot deallocate servers. Cannot deallocate server(s) { [serverList] }.

51N44

Status description: error: system configuration or operation exception - cannot drop server. Cannot drop server { [server] }.

51N45

Status description: error: system configuration or operation exception - cannot cordon server. Cannot cordon server { [server] }.

51N46

Status description: error: system configuration or operation exception - cannot alter server. Cannot alter server { [server] }.

51N47

Status description: error: system configuration or operation exception - cannot rename server. Cannot rename server { [server] }.

51N48

Status description: error: system configuration or operation exception - cannot enable server. Cannot enable server { [server] }.

51N49

Status description: error: system configuration or operation exception - cannot alter database. Cannot alter database { [db] }.

51N50

Status description: error: system configuration or operation exception - cannot recreate database. Cannot recreate database { [db] }.

51N51

Status description: error: system configuration or operation exception - cannot create database. Cannot create database { [db] }.

51N52

Status description: error: system configuration or operation exception - number of primaries out of range. Cannot { [action] } database topology. Number of primaries { [count] } needs to be at least 1 and may not exceed { [upper] }.

51N53

Status description: error: system configuration or operation exception - number of secondaries out of range. Cannot { [action] } database topology. Number of secondaries { [count] } needs to be at least 0 and may not exceed { [upper] }.

51N54

Status description: error: system configuration or operation exception - cannot reallocate. Failed to calculate reallocation for databases. { [msg] }

51N55

Status description: error: system configuration or operation exception - cannot create additional database. Failed to create the database { [db] }. The limit of databases is reached. Either increase the limit using the config setting { [cfgSetting] } or drop a database.

51N56

Status description: error: system configuration or operation exception - topology out of range. The number of { [serverType] } seeding servers { [count]1 } is larger than the desired number of { [allocType] } allocations { $count2 }.

51N57

Status description: error: system configuration or operation exception - generic topology modification error. Unexpected error while picking allocations. { [msg] }

51N58

Status description: error: system configuration or operation exception - invalid shard topology. Invalid database shard topology. The number of { [context] } { [count] } needs to be at least 1 and may not exceed { [upper] }.

51N59

Status description: error: system configuration or operation exception - internal resource exhaustion. The DBMS is unable to handle the request, please retry later or contact the system operator. More information is present in the logs.

51N60

Status description: error: system configuration or operation exception - unable to check enterprise license acceptance. The DBMS is unable to determine the enterprise license acceptance status.

51N61

Status description: error: system configuration or operation exception - index population failed. Index { [idx] } population failed.

51N62

Status description: error: system configuration or operation exception - index is in a failed state. Unable to use index { [idx] } because it is in a failed state. See logs for more information.

51N63

Status description: error: system configuration or operation exception - index is still populating. Index { [idx] } is not ready yet. Wait until it finishes populating and retry the transaction.

51N64

Status description: error: system configuration or operation exception - index dropped while sampling. The index dropped while sampling.

51N65

Status description: error: system configuration or operation exception - vector index dimensionality mismatch. Vector index { [idx] } has a dimensionality of { [dim]1 }, but indexed vectors have { $dim2 }.

51N66

Status description: error: system configuration or operation exception - resource exhaustion. Insufficient resources to complete the request.

51N67

Status description: error: system configuration or operation exception - invalid CDC selector type. Unexpected CDC selector { [selectorType]1 } at { [input] }, expected selector to be a { [selectorType]2 } selector.

51N68

Status description: error: system configuration or operation exception - CDC is disabled for this database. Change Data Capture is not currently enabled for this database.

51N69

Status description: error: system configuration or operation exception - system database is immutable. It is not possible to perform { [operation] } on the system database.

51N70

Status description: error: system configuration or operation exception - bolt is not enabled. Cannot get routing table for { [db] } because Bolt is not enabled. Please update your configuration such that server.bolt.enabled is set to true.

51N71

Status description: error: system configuration or operation exception - unsupported operation of a sharded database. Feature: { [feat] } is not available in a sharded database.

51N72

Status description: error: system configuration or operation exception - memory pool out of memory. Failed to allocate memory in a memory pool. See { [cfgSetting] } in the neo4j.conf file.

51N73

Status description: error: system configuration or operation exception - transaction memory limit reached. The transaction uses more memory than is allowed. The maximum allowed size for a transaction can be configured with { [cfgSetting] } in the neo4j.conf file.

51N74

Status description: error: system configuration or operation exception - maximum number of transactions reached. Failed to start a new transaction. The limit of concurrent transactions is reached. Increase the number of concurrent transactions using { [cfgSetting] } in the neo4j.conf file.

51N76

Status description: error: system configuration or operation exception - upgrade failed. The upgrade to a new Neo4j version failed.

51N77

Status description: error: system configuration or operation exception - not supported in this store format. { [feat] } is not supported in { [storeFormat] } store format.

51N7A

Status description: error: system configuration or operation exception - no admin user candidate. No admin user candidate is found. Use neo4j-admin dbms set-default-admin to select a valid admin.

Procedure exceptions

Procedure exceptions occur when there is an error in executing a procedure, such as when the procedure execution fails due to a client error, when the procedure cannot be invoked on a primary, when the number of arguments to checkConnectivity is invalid, etc.

52N01

Status description: error: procedure exception - procedure execution timeout. Execution of the procedure { [proc] } timed out after { [timeAmount] } { [timeUnit] }.

52N02

Status description: error: procedure exception - procedure execution client error. Execution of the procedure { [proc] } failed due to a client error.

52N03

Status description: error: procedure exception - invalid procedure execution mode. Execution of the procedure { [proc] } failed due to an invalid specified execution mode { [procExeMode] }.

52N05

Status description: error: procedure exception - must invoke procedure on secondary. Cannot invoke procedure on this member because it is not a secondary for the database { [db] }.

52N06

Status description: error: procedure exception - invalid number of arguments to checkConnectivity. Unexpected number of arguments (expected 0-2 but received { [count] }).

52N07

Status description: error: procedure exception - invalid port argument to checkConnectivity. Unrecognised port name { [port] } (valid values are: { [portList] }.

52N08

Status description: error: procedure exception - invalid server id argument to checkConnectivity. Unable to parse server id { [server] }.

52N09

Status description: error: procedure exception - procedure execution database error. Execution of the procedure { [proc] } failed due to a database error.

52N10

Status description: error: procedure exception - invalid address key. An address key is included in the query string provided to the GetRoutingTableProcedure, but its value could not be parsed.

52N11

Status description: error: procedure exception - generic topology procedure error. An unexpected error has occurred: { [msg] }.

52N12

Status description: error: procedure exception - cannot change default database. The previous default database { [db] } is still running.

52N13

Status description: error: procedure exception - new default database does not exist. New default database { [db] } does not exist.

52N14

Status description: error: procedure exception - system cannot be default database. System database cannot be set as default.

52N16

Status description: error: procedure exception - invalid procedure argument list. Invalid arguments to procedure.

52N17

Status description: error: procedure exception - quarantine change failed. Setting/removing the quarantine marker failed: { [msg] }.

52N18

Status description: error: procedure exception - too many seeders. The number of seeding servers { [countSeeders] } is larger than the defined number of allocations { [countAllocs] }.

52N19

Status description: error: procedure exception - no such seeder. The specified seeding server with id { [server] } was not found. Verify that the spelling is correct.

52N21

Status description: error: procedure exception - failed to clean the system graph. Failed to clean the system graph.

52N22

Status description: error: procedure exception - invalid procedure argument. Invalid argument { [field] } for { [procParam] } on procedure { [proc] }. The expected format of { [procParam] } is { [procParamFmt] }.

52N23

Status description: error: procedure exception - non-reloadable namespace. The following namespaces are not reloadable: { [namespaceList] }

52N24

Status description: error: procedure exception - failed to reload procedures. Failed to reload procedures. See logs for more information.

52N25

Status description: error: procedure exception - JMX error. JMX error while accessing { [param] }. See logs for more information.

52N26

Status description: error: procedure exception - invalid change identifier. { [param] } is not a valid change identifier.

52N27

Status description: error: procedure exception - invalid commit timestamp. The commit timestamp for the provided transaction ID does not match the one in the transaction log.

52N28

Status description: error: procedure exception - invalid change identifier and transaction id. { [transactionId] } is not a valid change identifier. Transaction ID does not exist.

52N29

Status description: error: procedure exception - outdated change identifier. Given ChangeIdentifier describes a transaction that occurred before any enrichment records exist.

52N30

Status description: error: procedure exception - future change identifier. Given ChangeIdentifier describes a transaction that hasn’t yet occurred.

52N31

Status description: error: procedure exception - wrong database. Change identifier { [param] } does not belong to this database.

52N32

Status description: error: procedure exception - invalid sequence number. Change identifier { [param]1 } has an invalid sequence number { $param2 }.

52N33

Status description: error: procedure exception - procedure invocation failed. Failed to invoke procedure/function { [sig] } caused by: { [msg] }.

52N34

Status description: error: procedure exception - procedure restricted. { [fun] } is restricted and accesses database internals. Procedure restriction is controlled by the dbms.security.procedures.unrestricted setting. Only un-restrict procedures you can trust with access to database internals.

52N35

Status description: error: procedure exception - procedure compilation failed. Failed to compile procedure defined in { [procClass] }: { [msg] }

52N36

Status description: error: procedure exception - invalid procedure argument with API documentation hint. Invalid argument { [field] } for { [procParam] } on procedure { [proc] }. The expected format of { [procParam] } is outlined in the { [procParamFmt] } API documentation.

52N37

Status description: error: procedure exception - procedure execution error. Execution of the procedure { [proc] } failed.

52N38

Status description: error: procedure exception - cdc start position not found. Cannot find a start position in the logs.

52N39

Status description: error: procedure exception - cdc scanner inactive. The log scanner is no longer active.

52N40

Status description: error: procedure exception - Reconciliation failed during writing the topology graph, transaction may not be committed.

52N41

Status description: error: procedure exception - The key value for { [field] } in the query string cannot be parsed when getting a routing table.

52U00

Status description: error: procedure exception - custom procedure execution error cause. Execution of the procedure { [proc] } failed due to { [msgTitle] }: { [msg] }

Function exceptions

53N33

Status description: error: function exception - function invocation failed. Failed to invoke function { [sig] } caused by: { [msg] }

53N34

Status description: error: function exception - function restricted. { [fun] } is restricted and accesses database internals. User-defined function restriction is controlled by the dbms.security.procedures.unrestricted setting. Only un-restrict user-defined functions you can trust with access to database internals.

53N35

Status description: error: function exception - function compilation failed. Failed to compile function defined in { [funClass] }: { [msg] }

53N37

Status description: error: function exception - function execution error. Execution of the function { [fun] } failed.

53U00

Status description: error: function exception - custom function execution error cause. Execution of the function { [fun] } failed due to { [msgTitle] }: { [msg] }.

Dependent object errors

G1001

Status description: error: dependent object error - edges still exist

Glossary

partial$glossary.adoc

FilesExpand file tree

index.adoc

Latest commit

History

index.adoc

File metadata and controls

List of GQLSTATUS error codes

Connection exceptions

Data exceptions