Node.js Retry Design for E-commerce Webhooks Using Delayed Queues and Idempotency

The article explains how to retry a failed outbound e-commerce webhook in Node.js by publishing the retry to a delayed queue rather than handling it inline. It stresses that the receiving side must be idempotent, deduplicating by a stable event ID, because queues deliver at least once and a timeout is ambiguous rather than proof of failure. The author recommends a short initial delay with exponential backoff, a maximum attempt count, and a dead-letter path for human review. Retry timing should be tuned by measuring recovery latency against retry cost using the real delivery endpoint. The piece also notes platform limits on scheduled work, delayed messages, and retention, and includes sample code for a delayed publish.