Update modules/ROOT/pages/queries/composed-queries/sequential-queries.adoc

Co-authored-by: Jens Pryce-Åklundh <[email protected]>

Author: rsill-neo4j

modules/ROOT/pages/queries/composed-queries/sequential-queries.adoc

@@ -474,8 +474,28 @@ ELSE {
 The query above calculates the total price of products purchased per customer and then only applies the customer discount to sums below 1000.
 
 
-[[next-aggregations-in-union-and-call]]
-== `NEXT` and aggregations in the context of `UNION` and `CALL`
+[[issues-fixes]]
+== Known issues and fixes
+
+`NEXT` initially did not correctly handle aggregations in the context of `UNION` branches and `CALL` subqueries.
+As of Neo4j 2025.08, this issue has been fixed.
+The table below summarizes the behavior changes across versions.
+
+[[%header,cols="a,5a"]
+|===
+| Neo4j version 
+| Behavior
+
+| 2025.06
+| `NEXT` yields incorrect results when using aggregations in the context of `UNION` branches and `CALL` subqueries.
+
+| 2025.07
+| Using aggregations with `NEXT` in the context of `UNION` branches and `CALL` subqueries throws an error.
+
+| 2025.08+
+| `NEXT` correctly supports aggregations in the context of `UNION` branches and `CALL` subqueries.  
+See above for more details.
+|===
 
 As of Neo4j 2025.08, `NEXT` correctly supports aggregations in the context of `UNION` and `CALL`.
 In Neo4j 2025.06, such queries yielded incorrect results while they created an error in Neo4j 2025.07.