## TL;DR

Do not wrap the client in your own retry loop without knowing the default: transient 429s and 5xx are already retried twice. Tune maxRetries up for batch jobs or down when you want fast failure.

## Fix

1. Do not wrap the client in your own retry loop without knowing the default: transient 429s and 5xx are already retried twice.
   Expected: You get the expected result; the problem is gone.

## When to use

- You are setting up or using this Reducto Node SDK feature.
- The symptom matches: default retries cover 408, 409, 429 and 5xx, twice.

## When NOT to use

- Unrelated Reducto Node SDK issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against Reducto Node SDK.

## Variant phrasings

### default retries cover 408, 409, 429 and 5xx, twice

## Why it happens

Official docs (Reducto Node SDK README): documents that the client retries connection errors plus 408, 409, 429, and 5xx responses twice by default, with maxRetries configurable.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.