Verification | Trigger for Action Needed Email

[steele-lm]

Issue Description

For any async job where we've accepted the payload from the vets-website... if we've called an async job, meaning one that we aren't notifying the veteran of a failure, we need to do the following:

1. Log it.

You can use this lib/zero_silent_failures/monitor.rb to help you do the logging.
Here are examples of usage: https://github.com/department-of-veterans-affairs/vets-api/pull/18941/files

2. Send an email
   a. We should be able to get the VA-notify template ID's from Fiorella.

Also, here is some documentation that may help:
https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/maste[…]tform/practices/zero-silent-failures/logging-silent-failures.md

Resources

• VA Notify Platform Overview
• VA Notify GitHub
• VA Notify Playbook
• API docs
• Completing the "create trigger" tickets
• Forms Strike Team can assist with setting up a confirmation email trigger

---

Tasks

• - Building on the research and workflows from the mural, use the logging library to log the failure.
• -
• Test notification by logging into staging with a test user, updating the profile ID to something that sends to you
• Determine alerting and error handling if email fails to deliver
• Implement new statsd metric. See this write up.
• Update form flow diagram to include action needed email

Acceptance Criteria

• A notification trigger that sends an email to the address the claimant entered in the form when: (if no address is entered into the form, use their VA profile email)
  • Claim fails to establish through backup pathway (open question on how long to wait for success)
  • Evidence fails to upload (immediately)
  • Evidence fails to upload (days later) (open question on how long to wait for success)
• Logging and monitoring for failed sends
• New statsd metric implemented
• Form flow updated to include action needed email
• Turn on flipper in production