Offramp claims in given error handling scenarios

[dianagriffin]

User Story

As a VRO stakeholder, I want to have confidence that when claims cannot complete processing in VRO due to errors, the claims are appropriately offramped so that they will be processed manually by claim adjudicators.

Error scenarios

1. VRO identifies that a NEW claim is not presumptive (ie. does not have the Agent Orange Exposure Verified flash) - note this is technically not an error, and should still return 200 from /automatedClaims
   • Logs should record offramp reason: newClaimMissingFlash266
2. VRO cannot successfully retrieve annotation data via the MAS endpoint
   • Logs should record offramp reason: annotationDataRequestFailed
3. VRO cannot successfully request an exam order via the MAS endpoint
   • Logs should record offramp reason: examOrderFailed
4. BIP Claim Evidence API is down and the claim has sufficient evidence to be marked RFD (ie. did not request an exam)
   • Logs should record offramp reason: docUploadFailed

Acceptance Criteria

1. For each of the error scenarios listed above, offramp the claim by setting it to the state described in Update & confirm state of claim/contention fields when offramped #1286
2. For each of the error scenarios listed above, log the error and trigger a Slack notification to #benefits-vro-alerts that includes in the message field:
   • the Claim ID
   • the offrampReason

Notes about work

• https://github.com/department-of-veterans-affairs/abd-vro/wiki/iMVP-claim-and-contention-update-scenarios
• https://lighthouseva.slack.com/files/U03GVR68Q6L/F04UB2LNA86/mas-mcp_automated_claim_contract.docx
• Error scenarios spreadsheet