Dependents | Document 686C-674 Failure points

[tblackwe]

Recently, we realized that when the DependentsService fails for PDF Upload, we both notify the Veteran and submit the claim down back process.

Please document the various Failure scenarios that can occur in 686C-674 submissions, and what we do in each scenario https://app.mural.co/t/departmentofveteransaffairs9999/m/departmentofveteransaffairs9999/1697740873991/4be42fcadc013be6b3d65bd620522ee68e8e0faf?wid=0-1721321111054&sender=u0e23f90bc2aa6d1f44e99992

What happens when:

• vets-api is down
• vets-api controller unreachable
• SavedClaim cant be saved
• PDF cant be uploaded
• Evidence Upload fails
• 686 cant be submitted
• 674 cant be submitted
• backup submission fails
• backup submission succeeds, but polling job shows failure
• anything else I missed

Acceptance Criteria

This ticket is solely about addressing the dead-ends and potential opportunities for remediation of 686c/674. This is not a ticket about code quality or an effort to capture silent failures.

• [ ] - Present findings to product team for next steps.

[sanjabaj2]

Potential sub ticket, as one of the findings.

[mjknight50]

@evansmith - Is this actually done? What was the outcome?
If not, can we please move back to backlog?

[evansmith]

@mjknight50 I completed the mural board addition. I can move it to review.

[mjknight50]

We'll need to present out findings on 686c/674. Can you please link any tickets that were created as a result. If you are ready to present on this, we'll need to schedule a meeting with Sanja and Steve. cc @steele-lm

[evansmith]

@tblackwe do you know which tickets were created from this?

[steele-lm]

@evansmith @mjknight50 @tblackwe I believe we need to review the documentation created, determine where the gaps are, create tickets to mitigate/improve, and then meet with Sanja and Steve.

[steele-lm]

@mjknight50 to talk to @tblackwe about next steps.

[mjknight50]

This ticket is solely about addressing the dead-ends and potential opportunities for remediation of 686c/674. This is not a ticket about code quality or an effort to capture silent failures.

[sanjabaj2]

I created additional monitors as I worked on this ticket The outcome of the ticket should be to:

1. Document failure scenarios (i.e. mural)
2. Create tickets for identified shortcomings in error catching
3. Create tickets for identified shortcomings in monitors.

When this ticket is complete, we have good picture of work needed to be properly and accurately detecting and monitoring for silent failures.

[sanjabaj2]

Also, did someone edit acceptance criteria that I added couple weeks back?

[steele-lm]

Closing this as a duplicate of #93326 and #93327