Skip to content

feat(notifications): add max delay cap and 408 retry handling in email backoff (#1935) - #2075

Closed
ryder777777 wants to merge 1 commit into
Arena1X:mainfrom
ryder777777:fix-1935-email-retry-backoff
Closed

ryder777777 wants to merge 1 commit into
Arena1X:mainfrom
ryder777777:fix-1935-email-retry-backoff

Conversation

@ryder777777

Copy link
Copy Markdown

Closes #1935

Summary

Add a configurable maxDelayMs cap (DEFAULT_RETRY_MAX_DELAY_MS = 60000) and negative-attempt clamping to computeBackoffDelay, and classify HTTP 408 Request Timeout as a transient retryable status in isTransientHttpStatus.

Modified Files

  • backend/src/notifications/email.service.ts
  • backend/src/notifications/email.service.spec.ts

Verification

  • Verified with npx eslint (0 errors) and npx jest unit tests passing in backend/.

@ryder777777

Copy link
Copy Markdown
Author

/claim #1935

Payout Wallet (Binance USDT TRC20 / Tron Network): TXmG2bbkS5m2ZfT535o5kQNpwYzhb5JUYg

@vercel

vercel Bot commented Oct 20, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
insight-arena-4rll Error Error Oct 20, 2026 7:16pm UTC

This branch had an error being deployed

1 failed deployment
Preview — da608fdf Deployed Oct 20, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Backend] — Email Service Retry With Exponential Backoff

2 participants