Skip to content

Conversation

@ArtOfCode-
Copy link
Member

The AWS limit of 50 recipients was triggering because we were sending TO one address, BCC 50 others - 51 recipients.

Reduced chunk size to 49, which should solve the problem.

Closes #1724.

@ArtOfCode- ArtOfCode- requested a review from a team August 2, 2025 19:32
@ArtOfCode- ArtOfCode- added this to the v0.12.3 milestone Aug 2, 2025
@codecov
Copy link

codecov bot commented Aug 2, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.50%. Comparing base (8f917b1) to head (5ffa318).
⚠️ Report is 2 commits behind head on develop.

Additional details and impacted files
Components Coverage Δ
controllers 68.67% <100.00%> (-0.04%) ⬇️
helpers 79.01% <ø> (ø)
jobs 48.57% <ø> (ø)
models 85.86% <ø> (ø)

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Member

@Oaphi Oaphi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For reference, this is the SES quota in question (we use 1 email in TO + N in BCC, hence the adjusted limit):

50 recipients per message.
Note A recipient is any "To", "CC", or "BCC" address.

@Oaphi Oaphi merged commit 0cf65e1 into develop Aug 2, 2025
14 checks passed
@Oaphi Oaphi deleted the art/1724/email-chunks branch August 2, 2025 20:08
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.

Emails to all users don't send because they have too many recipients

2 participants