Email Async Backend

[isabellalam12]

Plan and implement asynchronous email backend and UI. Swap to database-backed templates.

Fix backend and frontent tests

Remove MatchingSendPage and dedupe sending

[isabellalam12]

• Email Async Backend #82 : 2 dependent PRs (#71 , #81 ) 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[graphite-app]

Critical Bug: Hard delete instead of soft delete

The softDelete method performs a hard DELETE instead of a soft delete (setting a deleted_at timestamp). This contradicts:

1. The method name and documentation in TemplateManagementService.java (line 80-82) which states it "soft-deletes a template"
2. The decision in docs/email-async/05-template-management.md which recommends "block delete if any row references it (or add a deleted_at soft-delete flag)"
3. The requirement to preserve audit history mentioned in the service layer

This will cause:

• Loss of audit trail when templates are deleted
• Potential FK constraint violations if emails reference the deleted template
• Inconsistency between documented and actual behavior

Fix:

@Override
public int softDelete(final UUID id) {
    return jdbc.sql("UPDATE email_templates SET deleted_at = NOW() WHERE id = :id AND deleted_at IS NULL")
            .param("id", id)
            .update();
}

Also add deleted_at TIMESTAMPTZ column to the email_templates table schema and update findAll() to filter out soft-deleted templates with WHERE deleted_at IS NULL.

Spotted by Graphite



Is this helpful? React 👍 or 👎 to let us know.

[graphite-app]

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.