Travel Advice or Drug and Medical Device email alerts not sent
There is a check to verify that emails are sent for drug and medical device alerts and travel advice updates. These checks are run via Jenkins: Drug and medical device alerts check and Travel advice alerts check.
Troubleshooting failed checks
First inspect the console logs for the Jenkins job to confirm the reason for the failure. The email check looks in two different mailboxes and the failure message should describe which mailbox is seeing an issue.
Check the mailbox that is used for the check to rule out an issue searching for the message:
firstname.lastname@example.orgThis email address is subscribed to travel advice alerts and drug and medical device alerts. Its credentials can be found in the 2nd line password store under
Check the courtesy copy inbox. Its presence here doesn’t mean that the email was sent to users, just that Email Alert API processed the content change.
If the email has been received by the mailbox but the subject of the email doesn’t match the title of the content item, this means that the title of the content was updated after it was first published and after the emails went out. To stop the check from constantly failing, add the updated content item title to the acknowledged email list and then re-run the Jenkins job.
Troubleshooting unsent emails
If the check is reporting correctly then emails are not being sent. Try the general troubleshooting tips for unsent emails.
Resending travel advice emails
If you need to force the sending of a travel advice email alert, there
is a rake task in Travel Advice Publisher, which you can run using
this Jenkins job where the edition ID of the
travel advice content item can be found in the URL of the country’s edit
page in Travel Advice Publisher and looks like