Recovery Plan for Potentially Missing Renewal Emails After Apr 24 Production Deployment

Following the production deployment on Apr 24, some (potentially all) renewal notification emails were not sent due to a mismatch in component versions.

As a result:

- HMA manually sent the 1-day renewal notifications yesterday for registrations expiring today.
- There are 2 registrations expiring tomorrow (Sat,May 9) that may be used for validation/testing purposes.
- More than 300 renewals scheduled for Monday may also be impacted.

Tasks / Required Actions

**Validate renewal email functionality**

- Determine whether renewal emails are now being triggered correctly following the deployment.
- Confirm whether the 2 registrations expiring tomorrow can be used to verify successful email generation and delivery.
- If renewal emails are confirmed to be functioning correctly, no further remediation may be required; however, we need a high degree of confidence before Monday’s 300+ renewals are processed.

**Assess selective re-triggering of renewal notifications**

- We can re-trigger the 40-day and 14-day renewal notifications if needed.
- However, we want to avoid sending renewal emails for registrations that have already expired since Apr 24
- Determine whether there is a way to identify affected registrations and selectively re-trigger notifications only for valid/non-expired registrations.

**Non-renewal emails**

- It is acceptable to re-trigger other non-renewal email types (e.g., cancellations) if required.