Node.js: Best pattern to retry failed API calls without creating duplicate side effects?

"The outbox pattern works by storing the request fingerprint, original payload, and processing state before making the API call. On timeout, query the outbox to determine if this exact request was already processed. If yes, return cached result. If no, retry safely. Use a fingerprint hash of method, endpoint, and request body to identify duplicates. Set a deduplication window (e.g., 24 hours) to balance safety with storage."

"Implement exponential backoff with jitter for retries: first retry after 1 second, then 2, 4, 8 seconds with ±10% jitter. Log at each retry decision point: timeout detected, outbox lookup result, retry attempt number, and final outcome. Emit metrics for retry_attempts, dedup_hits, timeout_rate, and api_latency_p99 to track provider behavior patterns and identify systematic issues."

"Handle provider inconsistency by polling the provider's status endpoint or webhook callbacks if available. If the provider confirms processing after your timeout, update the outbox record to mark as processed and return the confirmed result. If no confirmation arrives within the deduplication window, treat as failed and allow new attempts. This graceful degradation handles both reliable and unreliable providers."

When third-party APIs timeout without confirming request processing, blind retries risk duplicate resource creation. The most practical production approach combines an outbox table storing request fingerprints with deduplication logic, allowing safe retries within a defined window. Store the original request, its fingerprint hash, and processing state before calling the API. On timeout or 5xx errors, check if an identical request exists in the outbox within the deduplication window. If found and already processed, return the cached result. If pending, retry. If expired, treat as new. Implement exponential backoff with jitter, add comprehensive logging at each decision point, and emit metrics tracking retry attempts, deduplication hits, and timeout patterns. This approach provides observability while preventing duplicates without requiring provider-side idempotency support.

Read at SitePoint Forums | Web Development & Design Community