Email Async Backend - #82
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
114d7ce to
ce53f24
Compare
75f0444 to
6e2e2a1
Compare
ce53f24 to
56fc6a4
Compare
Plan and implement asynchronous email backend and UI. Swap to database-backed templates. Fix backend and frontent tests Remove MatchingSendPage and dedupe sending
56fc6a4 to
4fce3f3
Compare
d14ca7a to
ebd603a
Compare
|
Graphite Automations"Request reviewers once CI passes" took an action on this PR • (08/19/26)2 reviewers were added to this PR based on Henry Chen's automation. |
Merge activity
|
| } | ||
|
|
||
| // Async email flow with template ID (replaces SendRequest for new code) | ||
| export interface SendAsyncRequest { |
There was a problem hiding this comment.
Note here that this can be used for both the legacy (non async) and new async paths.
We may want to add the ability in the future to send emails without a template (adhoc custom message) but saving everything as a template is fine for now.
| @Slf4j | ||
| public class EmailDrainer { | ||
|
|
||
| private static final int BATCH_SIZE = 50; |
There was a problem hiding this comment.
Nit for the future - ideally make something like this configurable based on our pairings size.
Can live in a conf file/env var so we can tweak it easily without redeploying the code
Plan and implement asynchronous email backend and UI. Swap to database-backed templates. Fix backend and frontent tests Remove MatchingSendPage and dedupe sending




Plan and implement asynchronous email backend and UI. Swap to database-backed templates.
Fix backend and frontent tests
Remove MatchingSendPage and dedupe sending