| owner_slack | title | section | subsection | layout | parent | last_reviewed_on | review_in |
|---|---|---|---|---|---|---|---|
#govuk-2ndline |
Email Alert API: High number of delivery attempts |
Icinga alerts |
Email alerts |
manual_layout |
/manual.html |
2020-07-16 |
6 months |
The first thing to do is determine what kind of failure is affecting the delivery attempts.
This means that we鈥檝e failed to make a request to Notify within the last hour due to a problem in our code. The reason for this failure should be visible in Sentry.
This means that we鈥檝e received a technical failure status code back from Notify or a request to send an email via Notify failed within the last hour. This means that there may be a problem with our system or that Notify is unable to send emails.
Emails given a technical_failure status will not be retried automatically.
To retry these you will need to use the resend tasks.
In non-production environments, this failure may also mean that we鈥檙e attempting to send emails to people who are not members of the Notify team for the relevant environment.
In this case, ensure the contents of the
govuk::apps::email_alert_api::email_address_override_whitelist key in
hieradata and hieradata_aws matches the members of the
staging/integration Notify teams.
You can login to the Notify account by going to the
GOV.UK Notify Admin Interface. The login credentials are in the
2nd line password store under
govuk-notify/2nd-line-support.
Read email troubleshooting.