department-of-veterans-affairs / va.gov-team

Public resources for building on and in support of VA.gov. Visit complete Knowledge Hub:
https://depo-platform-documentation.scrollhelp.site/index.html
283 stars 204 forks source link

Discover Veteran Evidence Doc silent failures #88534

Open lisacapaccioli opened 3 months ago

lisacapaccioli commented 3 months ago

Discovery/Knowability for Veteran Evidence Document Upload Historical Silent Failures The purpose of this Discovery is to uncover the impact of the silent upload failures and report them to OCTO and VBA.

OCTO needs to know how many Veteran evidence uploads ~and 0781~ silent failures there are since 526 was launched in August 2018. The last day of the "silent failure" timeline should be the first day [TBD] is launched.

The outcome of this phase should be an artifact that shows when logs are available, and what information we have, and volume counts. See: CY3 knowability table and log timeline for an example of the type of information we'll need. Can be a doc, table, diagram, or a combination.

This will help VBA make decisions on what to do with the data we have. We likely won't be resubmitting anything on our own, directly into the efolders. Why? Because without an EP, no one will know to look at and re-review it. This process will mirror other code yellows in that we'll be creating spreadsheets, delivering documents, and working with VBA to take action.

Goals

The discovery work should solve for these:

Dependency

We may need help from CorpDB or VBMS database folks to compare what was submitted to what ultimately arrived.

lisacapaccioli commented 3 months ago

0781 failures should be separate as they are not related to the historical evidence upload failures. I crossed out that in the above so that we could focus on evidence uploads. If we need numbers for the 0781 and 0781a we will do that separately, maybe as part of the mail notification for 0781/a.

lisacapaccioli commented 4 weeks ago

Current status as of 10/4/24 We delivered a list of suspected silent failures along with a report that summarizes the findings, process, and limitations on assuredness, erroring on the side of identifying as a failure a file that may have actually made it to the eFolder. Work still remains to share the files, when the decision is made as to how that will be done.

The majority of the identified silent failures were programmatically determined to be accessible. Possible solutions for the remediation process: