Skip to content
Original file line number Diff line number Diff line change
Expand Up @@ -296,6 +296,34 @@ RETURN cosh(0.5), coth(0.5), sinh(0.5), tanh(0.5)
For more information, see xref:functions/mathematical-trigonometric.adoc[Mathematical functions - trigonometric].
|===

[[cypher-deprecations-additions-removals-2025.03]]
== Neo4j 2025.03

=== New features

[cols="2", options="header"]
|===
| Feature
| Details

a|
label:functionality[]
label:new[]
[source, cypher, role=noheader]
----
UNWIND range(1, 100) AS i
CALL (i) {
MERGE (u:User {id: i})
ON CREATE SET u.created = timestamp()
} IN TRANSACTIONS ON ERROR RETRY 1 SECOND THEN FAIL
----

| New error handling option for `CALL { ... } IN TRANSACTIONS`: `ON ERROR RETRY`.
This option applies an exponential delay between retries for transaction batches failing due to transient errors, with an optional maximum retry duration, and handles failure based on a specified fallback error mode if the transaction does not succeed within the given time.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The retry logic is currently exponential backoff with some random jitter, but I am not sure if we need to go into that level of detail anywhere (maybe compare with driver docs?)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can skip this. The driver docs doesn't go into details either.

For more information, see xref:subqueries/subqueries-in-transactions#on-error-retry[`CALL` subqueries in transactions -> `ON ERROR RETRY`].

|===

[[cypher-deprecations-additions-removals-2025.01]]
== Neo4j 2025.01

Expand Down
Loading