neo4j · renetapopova · Sep 29, 2025 · Feb 5, 2025 · Feb 10, 2025 · Feb 10, 2025
diff --git a/antora.yml b/antora.yml
@@ -1,12 +1,12 @@
 name: status-codes
 title: Status Codes for Errors & Notifications
-version: '2025.08'
+version: '2025.09'
 start_page: ROOT:index.adoc
 nav:
 - modules/ROOT/content-nav.adoc
 asciidoc:
   attributes:
     page-origin-private: false
-    neo4j-version: '2025.08'
-    neo4j-version-exact: '2025.08.0'
-    neo4j-buildnumber: '2025.08'
+    neo4j-version: '2025.09'
+    neo4j-version-exact: '2025.09.0'
+    neo4j-buildnumber: '2025.09'
diff --git a/modules/ROOT/content-nav.adoc b/modules/ROOT/content-nav.adoc
@@ -95,6 +95,7 @@
 **** xref:errors/gql-errors/22N57.adoc[]
 **** xref:errors/gql-errors/22N58.adoc[]
 **** xref:errors/gql-errors/22N59.adoc[]
+**** xref:errors/gql-errors/22N60.adoc[]
 **** xref:errors/gql-errors/22N62.adoc[]
 **** xref:errors/gql-errors/22N63.adoc[]
 **** xref:errors/gql-errors/22N64.adoc[]
@@ -156,6 +157,8 @@
 **** xref:errors/gql-errors/22NBA.adoc[]
 **** xref:errors/gql-errors/22NBC.adoc[]
 **** xref:errors/gql-errors/22NBD.adoc[]
+**** xref:errors/gql-errors/22NBE.adoc[]
+**** xref:errors/gql-errors/22NBF.adoc[]
 *** xref:errors/gql-errors/index.adoc#invalid-transaction-state[Invalid transaction state]
 **** xref:errors/gql-errors/25G02.adoc[]
 **** xref:errors/gql-errors/25N01.adoc[]
@@ -259,6 +262,9 @@
 **** xref:errors/gql-errors/42I62.adoc[]
 **** xref:errors/gql-errors/42I63.adoc[]
 **** xref:errors/gql-errors/42I64.adoc[]
+**** xref:errors/gql-errors/42I65.adoc[]
+**** xref:errors/gql-errors/42I66.adoc[]
+**** xref:errors/gql-errors/42I67.adoc[]
 **** xref:errors/gql-errors/42N00.adoc[]
 **** xref:errors/gql-errors/42N01.adoc[]
 **** xref:errors/gql-errors/42N02.adoc[]

diff --git a/modules/ROOT/pages/errors/gql-errors/22N60.adoc b/modules/ROOT/pages/errors/gql-errors/22N60.adoc
@@ -0,0 +1,18 @@
+:page-role: new-2025.09
+= 22N60
+
+== Status description
+error: data exception - illegal element. Encountered illegal `{ <<item>> }` element. Reason: `{ <<msg>> }`
+
+== Example of a status description
+
+[source]
+----
+error: data exception - illegal element. Encountered illegal root element. Reason: Expected struct.
+----
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]
diff --git a/modules/ROOT/pages/errors/gql-errors/22NBE.adoc b/modules/ROOT/pages/errors/gql-errors/22NBE.adoc
@@ -0,0 +1,17 @@
+:page-role: new-2025.09
+
+= 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 }`.
+
+== Scenario
+
+This error occurs when the server receives a vector value from a driver and that vector value has an unsupported number of dimensions.
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]
diff --git a/modules/ROOT/pages/errors/gql-errors/22NBF.adoc b/modules/ROOT/pages/errors/gql-errors/22NBF.adoc
@@ -0,0 +1,17 @@
+:page-role: new-2025.09
+
+= 22NBF
+
+== Status description
+error: data exception - property value too big. Property value of type `{ <<typeDescription>> }` is too big (more than `{ <<bytes>> }` bytes): `{ <<value>> }`
+
+== Scenario
+
+This error occurs when a property value cannot be stored because its size exceeds the limit.
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]
diff --git a/modules/ROOT/pages/errors/gql-errors/42I65.adoc b/modules/ROOT/pages/errors/gql-errors/42I65.adoc
@@ -0,0 +1,31 @@
+:page-role: new-2025.09
+= 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>> }`.
+
+== Example scenario
+
+For example, when trying to format using a year character on a time-only type:
+
+[source,cypher]
+----
+RETURN format(time(), "yyyy") AS formatted
+----
+
+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/42I65.adoc[42I65] and status description:
+
+
+[source]
+----
+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 `ZONED TIME`.
+----
+
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]
diff --git a/modules/ROOT/pages/errors/gql-errors/42I66.adoc b/modules/ROOT/pages/errors/gql-errors/42I66.adoc
@@ -0,0 +1,31 @@
+:page-role: new-2025.09
+= 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.
+
+== Example scenario
+
+For example, when formatting a duration:
+
+[source,cypher]
+----
+RETURN format(duration("P1Y"), "y 'year")
+----
+
+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/42I66.adoc[42I66] and status description:
+
+
+[source]
+----
+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.
+----
+
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]
diff --git a/modules/ROOT/pages/errors/gql-errors/42I67.adoc b/modules/ROOT/pages/errors/gql-errors/42I67.adoc
@@ -0,0 +1,40 @@
+:page-role: new-2025.09
+= 42I67
+
+== Status description
+error: syntax error or access rule violation - unsupported language feature. The query is a valid `CYPHER { <<feat>>2 }` query, but it is run in `CYPHER { <<feat>>1 }`. Consider changing the database default Cypher version using `ALTER DATABASE SET DEFAULT LANGUAGE` or prefix the query with `CYPHER { <<feat>>2 }`.
+
+== Example scenario
+
+For example, when using `LET` in a Cypher 5 query:
+
+[source,cypher]
+----
+CYPHER 5
+LET x = 1
+RETURN 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/42I67.adoc[42I67] and status description:
+
+
+[source]
+----
+error: syntax error or access rule violation - unsupported language feature. The query is a valid `CYPHER 25` query, but it is run in `CYPHER 5`. Consider changing the database default Cypher version using `ALTER DATABASE SET DEFAULT LANGUAGE` or prefix the query with `CYPHER 25`.
+----
+
+As well as a cause detailed in xref:errors/gql-errors/42I06.adoc[42I06] and status description:
+
+[source]
+----
+error: syntax error or access rule violation - invalid input. Invalid input 'LET', expected: 'ALTER', 'ORDER BY', 'CALL', 'USING PERIODIC COMMIT', 'CREATE', 'LOAD CSV', 'START DATABASE', 'STOP DATABASE', 'DEALLOCATE', 'DELETE', 'DENY', 'DETACH', 'DROP', 'DRYRUN', 'FINISH', 'FOREACH', 'GRANT', 'INSERT', 'LIMIT', 'MATCH', 'MERGE', 'NODETACH', 'OFFSET', 'OPTIONAL', 'REALLOCATE', 'REMOVE', 'RENAME', 'RETURN', 'REVOKE', 'ENABLE SERVER', 'SET', 'SHOW', 'SKIP', 'TERMINATE', 'UNWIND', 'USE' or 'WITH'.
+----
+
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]
diff --git a/modules/ROOT/pages/errors/gql-errors/index.adoc b/modules/ROOT/pages/errors/gql-errors/index.adoc
@@ -386,6 +386,11 @@ Status description:: error: data exception - invalid spatial component. Cannot r
 
 Status description:: error: data exception - token does not exist. The `{ <<tokenType>> }` token with id `{ <<tokenId>> }` does not exist.
 
+[role=label--new-2025.09]
+=== xref:errors/gql-errors/22N60.adoc[22N60]
+
+Status description:: error: data exception - illegal element. Encountered illegal `{ <<item>> }` element. Reason: `{ <<msg>> }`
+
 === xref:errors/gql-errors/22N62.adoc[22N62]
 
 Status description:: error: data exception - relationship type does not exist. The relationship type `{ <<relType>> }` does not exist.
@@ -629,9 +634,20 @@ Status description:: error: data exception - omitting mandatory field for proper
 
 Status description:: error: data exception - index belongs to constraint. Index belongs to constraint `{ <<constrDescrOrName>> }`.
 
+[role=label--new-2025.07]
 === xref:errors/gql-errors/22NBD.adoc[22NBD]
 
-Status description:: error: data exception - unsupported struct tag. Unsupported struct tag: 0x56. `{ <<value>> }`.
+Status description:: error: data exception - unsupported struct tag. Unsupported struct tag: `{ <<value>> }`.
+
+[role=label--new-2025.09]
+=== xref:errors/gql-errors/22NBE.adoc[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 }`.
+
+[role=label--new-2025.09]
+=== xref:errors/gql-errors/22NBF.adoc[22NBF]
+
+Status description:: error: data exception - property value too big. Property value of type `{ <<typeDescription>> }` is too big (more than `{ <<bytes>> }` bytes): `{ <<value>> }`
 
 
 [[invalid-transaction-state]]
@@ -1056,6 +1072,21 @@ Status description:: error: syntax error or access rule violation - wrong subcla
 
 Status description:: error: syntax error or access rule violation - unsupported operation. `{ <<msg>> }` currently not supported after `+NEXT+` `{ <<context>> }`.
 
+[role=label--new-2025.09]
+=== xref:errors/gql-errors/42I65.adoc[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>> }`.
+
+[role=label--new-2025.09]
+=== xref:errors/gql-errors/42I66.adoc[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.
+
+[role=label--new-2025.09]
+=== xref:errors/gql-errors/42I67.adoc[42I67]
+
+Status description:: error: syntax error or access rule violation - unsupported language feature. The query is a valid `CYPHER { <<feat>>2 }` query, but it is run in `CYPHER { <<feat>>1 }`. Consider changing the database default Cypher version using `ALTER DATABASE SET DEFAULT LANGUAGE` or prefix the query with `CYPHER { <<feat>>2 }`.
+
 [role=label--changed-2025.03]
 === xref:errors/gql-errors/42N00.adoc[42N00]
 

diff --git a/modules/ROOT/pages/notifications/all-notifications.adoc b/modules/ROOT/pages/notifications/all-notifications.adoc
@@ -1575,8 +1575,8 @@ Please use a path with a length of 1 [r*1..1] instead or a Match with a limit.
 - The query used a deprecated function. (`%s`)
 - The query used a deprecated procedure. (`%s`)
 - The query used a deprecated runtime option. (`%s`)
-- The `TextIndexProvider.DESCRIPTOR.name()` provider for text indexes is deprecated and will be removed in a future version.
-Please use `TrigramIndexProvider.DESCRIPTOR.name()` instead.
+-  `text-1.0` and `text-2.0` (from Neo4j 2025.09 onwards) providers for text indexes are deprecated and will be removed in a future version.
+Please use `text-3.0` instead.
 |Category
 m|DEPRECATION
 |GQLSTATUS code
@@ -5197,4 +5197,4 @@ ifndef::backend-pdf[]
 == Glossary
 
 include::partial$glossary.adoc[]
-endif::[]
+endif::[]
diff --git a/modules/ROOT/partials/glossary.adoc b/modules/ROOT/partials/glossary.adoc
@@ -10,6 +10,7 @@
 [[auth]]$auth:: Auth provider name, for example, `ldap`, `native`.
 [[boltServerState]]$boltServerState:: Bolt server state, for example, `READY`.
 [[boltMsgLenLimit]]$boltMsgLenLimit:: Bolt message length limit, for example, `1000`.
+[[bytes]]$bytes:: Number of bytes.
 [[cause]]$cause:: Freeform description of what caused the error.
 [[cfgSetting]]$cfgSetting:: Configuration setting key, for example, `server.https.enabled`.
 [[clause]]$clause:: A Cypher clause, for example, `USE`, `MATCH`.