Publish 2025.07

antora.yml

@@ -1,12 +1,12 @@
 name: status-codes
 title: Status Codes for Errors & Notifications
-version: '2025.06'
+version: '2025.07'
 start_page: ROOT:index.adoc
 nav:
 - modules/ROOT/content-nav.adoc
 asciidoc:
   attributes:
     page-origin-private: false
-    neo4j-version: '2025.06'
-    neo4j-version-exact: '2025.06.2'
-    neo4j-buildnumber: '2025.06'
+    neo4j-version: '2025.07'
+    neo4j-version-exact: '2025.07.0'
+    neo4j-buildnumber: '2025.07'

modules/ROOT/content-nav.adoc

@@ -141,6 +141,8 @@
 **** xref:errors/gql-errors/22NA7.adoc[]
 **** xref:errors/gql-errors/22NA8.adoc[]
 **** xref:errors/gql-errors/22NA9.adoc[]
+**** xref:errors/gql-errors/22NAA.adoc[]
+**** xref:errors/gql-errors/22NAB.adoc[]
 **** xref:errors/gql-errors/22NB0.adoc[]
 **** xref:errors/gql-errors/22NB1.adoc[]
 **** xref:errors/gql-errors/22NB2.adoc[]
@@ -254,6 +256,8 @@
 **** xref:errors/gql-errors/42I60.adoc[]
 **** xref:errors/gql-errors/42I61.adoc[]
 **** xref:errors/gql-errors/42I62.adoc[]
+**** xref:errors/gql-errors/42I63.adoc[]
+**** xref:errors/gql-errors/42I64.adoc[]
 **** xref:errors/gql-errors/42N00.adoc[]
 **** xref:errors/gql-errors/42N01.adoc[]
 **** xref:errors/gql-errors/42N02.adoc[]

modules/ROOT/pages/errors/gql-errors/22N69.adoc

@@ -1,7 +1,27 @@
+:page-role: changed-2025.07
+
 = 22N69
 
 == Status description
-error: data exception - index does not exist. The index specified by `{ <<idxDescrOrName>> }` does not exist.
+error: data exception - index does not exist. The index `{ <<idxDescrOrName>> }` does not exist.
+
+
+== Example scenario
+
+For example, try to drop a non-existing index:
+
+[source,cypher]
+----
+DROP INDEX `nonExisting`
+----
+
+You will receive an error with GQLSTATUS xref:errors/gql-errors/50N10.adoc[50N10].
+This error has a cause with GQLSTATUS 22N69 and status description:
+
+[source]
+----
+error: data exception - index does not exist. The index 'nonExisting' does not exist.
+----
 
 
 ifndef::backend-pdf[]

modules/ROOT/pages/errors/gql-errors/22N71.adoc

@@ -1,7 +1,33 @@
+:page-role: changed-2025.07
+
 = 22N71
 
 == Status description
-error: data exception - index with the same name already exists. An index with the same name already exists: `{ <<idx>> }`.
+error: data exception - duplicated index name. An index with the same name already exists: `{ <<idx>> }`.
+
+
+== Example scenario
+
+For example, try to create an index when there is another existing index with that name:
+
+Given:
+[source,cypher]
+----
+CREATE INDEX `myIndex` FOR (n:Person) ON (n.name)
+----
+
+Then, when attempting to create:
+[source,cypher]
+----
+CREATE INDEX `myIndex` FOR (n:Book) ON (n.title)
+----
+
+You will receive an error with GQLSTATUS 22N71 and status description:
+
+[source]
+----
+error: data exception - duplicated index name. An index with the same name already exists: `myIndex`
+----
 
 
 ifndef::backend-pdf[]

modules/ROOT/pages/errors/gql-errors/22NA0.adoc

@@ -1,7 +1,7 @@
 = 22NA0
 
 == Status description
-error: data exception - invalid property based access control rule. Failed to administer property rule.
+error: data exception - invalid property-based access control rule. Failed to administer property rule.
 
 ifndef::backend-pdf[]
 [discrete.glossary]

modules/ROOT/pages/errors/gql-errors/22NA1.adoc

@@ -2,7 +2,7 @@
 
 
 == 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.
+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.
 
 
 ifndef::backend-pdf[]

modules/ROOT/pages/errors/gql-errors/22NA2.adoc

@@ -2,7 +2,7 @@
 
 
 == 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.
+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.
 
 
 ifndef::backend-pdf[]

modules/ROOT/pages/errors/gql-errors/22NA3.adoc

@@ -2,7 +2,7 @@
 
 == Status description
 
-error: data exception - invalid property based access control rule involving NaN. 'NaN' is not supported for property-based access control.
+error: data exception - invalid property-based access control rule involving NaN. 'NaN' is not supported for property-based access control.
 
 
 

modules/ROOT/pages/errors/gql-errors/22NA4.adoc

@@ -1,7 +1,7 @@
 = 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`.
+error: data exception - invalid property-based access control rule involving comparison with `NULL`. The property value access rule pattern `{ <<pred>> }` always evaluates to `NULL`.
 
 ifndef::backend-pdf[]
 [discrete.glossary]

modules/ROOT/pages/errors/gql-errors/22NA5.adoc

@@ -1,7 +1,7 @@
 = 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.
+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.
 
 ifndef::backend-pdf[]
 [discrete.glossary]

modules/ROOT/pages/errors/gql-errors/22NA6.adoc

@@ -1,7 +1,7 @@
 = 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.
+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.
 
 ifndef::backend-pdf[]
 [discrete.glossary]

modules/ROOT/pages/errors/gql-errors/22NA7.adoc

@@ -2,7 +2,7 @@
 
 
 == 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.
+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.
 
 
 

modules/ROOT/pages/errors/gql-errors/22NAA.adoc

@@ -0,0 +1,28 @@
+= 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.
+
+== Example scenario
+
+For example, try to add a property-based access control rule including a list with a `NULL` type:
+
+[source,cypher]
+----
+GRANT TRAVERSE ON GRAPH * FOR (n) WHERE n.prop1 IN ["string value", NULL] TO role
+----
+
+You will receive an error with GQLSTATUS xref:errors/gql-errors/22NA0.adoc[22NA0]  and a cause with GQLSTATUS 22NAA and the following status description:
+
+
+[source]
+----
+error: data exception - invalid list for property-based access control rule. The expression 'n.prop1 IN ["string value", NULL]' is not supported. Lists containing NULL values are not supported for property-based access control.
+----
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]

modules/ROOT/pages/errors/gql-errors/22NAB.adoc

@@ -0,0 +1,28 @@
+= 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.
+
+== Example scenario
+
+For example, try to add a property-based access control rule that contains a list of mixed types:
+
+[source,cypher]
+----
+GRANT TRAVERSE ON GRAPH * FOR (n) WHERE n.prop1 IN ["string value", 5] TO role
+----
+
+You will receive an error with GQLSTATUS xref:errors/gql-errors/22NA0.adoc[22NA0] and a cause with GQLSTATUS 22NAB and the following status description:
+
+
+[source]
+----
+error: data exception - mixed type list for property-based access control rule. The expression 'n.prop1 IN ["string value", 5]' is not supported. All elements in a list must be literals of the same type for property-based access control.
+----
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]

modules/ROOT/pages/errors/gql-errors/22NB0.adoc

@@ -1,7 +1,7 @@
 = 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.
+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.
 
 ifndef::backend-pdf[]
 [discrete.glossary]

modules/ROOT/pages/errors/gql-errors/42I63.adoc

@@ -0,0 +1,33 @@
+= 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`.
+
+== Example scenario
+
+For example, try to use `ORDER BY` after `SKIP` and `LIMIT`:
+
+[source,cypher]
+----
+UNWIND [3,5,1,3,7,10] AS x
+RETURN x
+SKIP 2
+ORDER BY x
+----
+
+You will receive an error with GQLSTATUS xref:errors/gql-errors/42000.adoc[42000].
+This error has a cause detailed in xref:errors/gql-errors/42I63.adoc[42I63] and status description:
+
+
+[source]
+----
+error: syntax error or access rule violation - wrong subclause order. `ORDER BY`, `SKIP` and `LIMIT` can only be used in this order in `RETURN`.
+----
+
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]

modules/ROOT/pages/errors/gql-errors/42I64.adoc

@@ -0,0 +1,37 @@
+= 42I64
+
+== Status description
+error: syntax error or access rule violation - unsupported operation. `{ <<msg>> }` currently not supported after `+NEXT+` `{ <<context>> }`.
+
+== Example scenario
+
+For example, when aggregating in a `UNION` query after a `NEXT`:
+
+[source,cypher]
+----
+UNWIND [1, 2] AS x
+RETURN x
+
+NEXT
+
+RETURN COUNT(x)
+UNION ALL
+RETURN COUNT(x)
+----
+
+You will receive an error with GQLSTATUS xref:errors/gql-errors/42001.adoc[42001].
+This error has a cause detailed in xref:errors/gql-errors/42I64.adoc[42I64] and status description:
+
+
+[source]
+----
+error: syntax error or access rule violation - unsupported operation. Aggregations are currently not supported in `NEXT` when used in a `UNION`.
+----
+
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]

modules/ROOT/pages/errors/gql-errors/51N52.adoc

@@ -1,7 +1,13 @@
+:page-role: changed-2025.07
+
 = 51N52
 
 == Status description
-error: system configuration or operation exception - number of primaries out of range. Cannot alter database topology.  Number of primaries `{ <<count>> }` needs to be at least 1 and may not exceed `{ <<upper>> }`.
+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>> }`.
+
+== Explanation
+
+This error occurs when trying to create or alter a database while providing a topology with primary count outside the supported range.
 
 ifndef::backend-pdf[]
 [discrete.glossary]

modules/ROOT/pages/errors/gql-errors/51N53.adoc

@@ -1,7 +1,13 @@
+:page-role: changed-2025.07
+
 = 51N53
 
 == Status description
-error: system configuration or operation exception - number of secondaries out of range. Cannot alter database topology. Number of secondaries `{ <<count>> }` needs to be at least 0 and may not exceed `{ <<upper>> }`.
+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>> }`.
+
+== Explanation
+
+This error occurs when trying to create or alter a database while providing a topology with secondary count outside the supported range.
 
 ifndef::backend-pdf[]
 [discrete.glossary]

modules/ROOT/pages/errors/gql-errors/51N77.adoc

@@ -0,0 +1,20 @@
+= 51N77
+
+== Status description
+
+error: system configuration or operation exception - not supported in this store format. `{ <<feat>> }` is not supported in `{ <<storeFormat>> }` store format.
+
+== Scenario
+
+This error code is used when the user tries to use a feature that is unsupported by the store format, e.g. writing a property with an unsupported data type.
+
+== Possible solution
+
+Use a supported data type, or use a different store format.
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]