Closed lisacapaccioli closed 3 weeks ago
@pacerwow @emilytheis - Team Carbs has capacity to do this now. We've assigned to Scott for Sprint 40.
Datadog query covering last 15 months returned 14 results for "Submit Form 0781 Retries exhausted", 1 on 8/31 and the others over an ~12 hour period between 1/19 and 1/20, all before the Form0781DocumentUploadFailureEmail
was incorporated on 10/8.
Form526JobStatus.where(job_class: 'SubmitForm0781').where.not(status: %w[success retryable_error try])
Form526JobStatus.where(job_class: 'SubmitForm0781').where(status: %w[retryable_error try]).where('updated_at < ?', 2.days.ago)
195,623 Form526JobStatus.where(job_class: 'SubmitForm0781')
records
194,701 Form526JobStatus.where(job_class: 'SubmitForm0781').where(status: 'success')
records
difference of 922 records
PDF is generated from 0781/a data, then uploaded to EVSS Documents Service, which transfers to VBMS/eFolder.
Within eFolder, documentTypeLabel
types, both with originalFileName
values that are SecureRandom.hex
:
*_Verify that claimant's eFolder does not include document type?_**
Available data:
Form526JobStatus
attributes:
form526_submission_id
error_message
updated_at
Form526Submission
attributes:
user_uuid
saved_claim_id
submitted_claim_id
form_json
Fields to be included in generated CSV:
Form526JobStatus
with unsuccessful statusSavedClaim
'created_at' timestampForm526Submission
'user_uuid'documentTypeLabel
is present in associated eFolderdocumentTypeLabel
is present in associated eFolder'form0781' hash in form json may include:
Draft report of Form 21-0781/a Silent Failure Discovery complete.
We have confirmed that there are silent failures of 0781, 14 in the last year. And assumed more going back to when it launched.
This thread reveals that 0781 has not had any historical silent failure investigation and remediation work since the date it launched, and that it has failed silently. It needs the "full treatment" that we gave to evidence upload failures -- finding all the old ones, regenerating them, confirming the volume, and getting them to VBA.
The outcome of this phase should be an artifact that shows when logs are available, and what information we have, and volume counts.
The discovery work should solve for these:
0781
TBD
0781a
TBD
Out of scope for this Epic
Notes 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.
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.
If the total volume is less than 100 or so, VBA OFO may be willing to handle them in the manual upload/emergency failsafe process.