# Amazon DocumentDB adds retryable writes in engine 8.0.2

> DocumentDB 8.0.2 supports one automatic driver retry for eligible writes on instance-based and serverless clusters. Older engines still require retryable writes to be disabled.

Canonical URL: https://www.devobs.io/news/news-event-0f0f8dda1dc485bc71d3d39a/
By: Ines Costa
Published: 2026-10-01T21:27:59.300Z
Updated: 2026-10-01T21:27:59.300Z
Event date: 2026-09-28
Section: Data

Amazon DocumentDB supports retryable writes starting with engine version 8.0.2, AWS [announced on September 28, 2026](https://aws.amazon.com/about-aws/whats-new/2026/09/amazon-documentdb-retryable-writes/). The capability lets MongoDB-compatible drivers automatically retry eligible write operations once after a transient error, such as a network interruption or primary failover.

## Availability and version boundary

According to AWS, retryable writes are available on **DocumentDB 8.0.2 instance-based and serverless clusters**, in **all AWS Regions where DocumentDB 8.0 is available**. Engine versions earlier than 8.0.2 remain unsupported and require retryable writes to be disabled.

Most current MongoDB-compatible drivers enable retryable writes by default, AWS says. Applications connecting to 8.0.2 no longer need the `retryWrites=false` connection-string setting to avoid errors. AWS also says enabling the capability requires no additional code changes.

## Retry limits

This is a bounded retry mechanism, not an unlimited retry loop. The driver retries an eligible operation only once. [AWS explicitly excludes `updateMany` and `deleteMany`](https://aws.amazon.com/about-aws/whats-new/2026/09/amazon-documentdb-retryable-writes/), so applications using those multi-document commands should not assume that retryable writes cover them.

## Rollout checks

For teams operating mixed engine versions, review configuration by destination cluster rather than changing every connection string at once. Check both connection strings and driver settings before removing the disabling flag: the new capability does not change the requirement to disable retryable writes on older engines.

In a test environment, exercise an eligible write during a transient failure and verify how the application handles a failure that persists after the driver's single retry. Keep application-level error handling, and assess commands outside the retryable-write scope separately. The feature can simplify handling of eligible transient failures, but should not be treated as a guarantee that every write will succeed.

## Source references

- <https://aws.amazon.com/about-aws/whats-new/2026/09/amazon-documentdb-retryable-writes/>