diff --git a/modules/ROOT/content-nav.adoc b/modules/ROOT/content-nav.adoc
index 707b6ff1..16bd9434 100644
--- a/modules/ROOT/content-nav.adoc
+++ b/modules/ROOT/content-nav.adoc
@@ -254,6 +254,7 @@
 **** 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[]
diff --git a/modules/ROOT/pages/errors/gql-errors/42I63.adoc b/modules/ROOT/pages/errors/gql-errors/42I63.adoc
new file mode 100644
index 00000000..390360b8
--- /dev/null
+++ b/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::[]
diff --git a/modules/ROOT/pages/errors/gql-errors/42I64.adoc b/modules/ROOT/pages/errors/gql-errors/42I64.adoc
index f47025fd..eec43c6a 100644
--- a/modules/ROOT/pages/errors/gql-errors/42I64.adoc
+++ b/modules/ROOT/pages/errors/gql-errors/42I64.adoc
@@ -1,7 +1,7 @@
 = 42I64
 
 == Status description
-error: syntax error or access rule violation - unsupported aggregation. { <<msg>> } currently not supported after `NEXT` { <<context>> }.
+error: syntax error or access rule violation - unsupported aggregation. `{ <<msg>> }` currently not supported after `+NEXT+` `{ <<context>> }`.
 
 == Example scenario
 
diff --git a/modules/ROOT/pages/errors/gql-errors/index.adoc b/modules/ROOT/pages/errors/gql-errors/index.adoc
index 1ea28f79..613811cd 100644
--- a/modules/ROOT/pages/errors/gql-errors/index.adoc
+++ b/modules/ROOT/pages/errors/gql-errors/index.adoc
@@ -1034,9 +1034,13 @@ Status description:: error: syntax error or access rule violation - missing LOOK
 
 Status description:: error: syntax error or access rule violation - unsupported distance metric. Unknown distance metric:  `{ <<input>> }`.
 
+=== xref:errors/gql-errors/42I63.adoc[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`.
+
 === xref:errors/gql-errors/42I64.adoc[42I64]
 
-Status description:: error: syntax error or access rule violation - unsupported aggregation. { <<msg>> } currently not supported in `NEXT` { <<context>> }.
+Status description:: error: syntax error or access rule violation - unsupported aggregation. `{ <<msg>> }` currently not supported after `+NEXT+` `{ <<context>> }`.
 
 [role=label--changed-2025.03]
 === xref:errors/gql-errors/42N00.adoc[42N00]