#memoized

Can @Memoized prevent duplicate writes when a Groovy retry re-invokes a side-effecting method?

Groovy (assuming the 4.x line) has no standard retry primitive with idempotency guarantees, so retry logic around a failing write is usually hand-rolled as a closure inside a try/catch loop. Because a closure re-executes its captured side effects on each invocation, every retry attempt repeats the write unless the block is made idempotent by hand. @Memoized