Errors and incidents
Things that are broken or being watched. Every entry names the people affected and the next human step.
- Open incidents
- 2Needing action now
- Being monitored
- 1Fix in test or under observation
- Submissions affected
- 22Across all unresolved incidents
Nothing here silently changed a claim
When a mapping cannot be reconciled, the write is refused and an incident is opened rather than a value being guessed. Every item below waits on a person.
Showing 5 of 5 incidents.
INC-2026-0031HighOpen
Dependent writes rejected on a date-of-birth conflict
Four 21-686c submissions could not be written because the dependent date of birth differs from the award record. The mapping refuses to overwrite a record it cannot reconcile.
- System
- Corporate database - Award dependents
- Owner
- Dependency team
- Opened
- August 5, 2026
- Submissions affected
- 4
Next human step
A reviewer compares the submitted evidence against the award record and corrects one side by hand.
INC-2026-0029MediumMonitoring
Reader timeouts on scans over 40 pages
Uploads over roughly 40 pages exceed the reading window and fall back to manual entry. The upload itself always succeeds; only the pre-fill is skipped.
- System
- Document reader
- Owner
- Document services
- Opened
- August 2, 2026
- Submissions affected
- 11
Next human step
Page-range splitting is in test. Watch the fallback rate through the end of the week.
INC-2026-0027MediumOpen
Third-party links expiring before providers respond
Seven routed 21-2680 sections expired unanswered at 14 days. Providers opened the link but did not finish in one sitting, and there is no resume path after expiry.
- System
- Third-party routing
- Owner
- Routing team
- Opened
- July 29, 2026
- Submissions affected
- 7
Next human step
Veterans can re-issue a link from the tracker. A saved-progress option for providers is being scoped.
INC-2026-0024LowResolved
Schema mismatch after the 21-0966 June revision
The published schema still referenced two boxes that moved in the June paper revision, so those answers landed unmapped.
- System
- Intake and automation
- Owner
- Intake team
- Opened
- July 18, 2026
- Submissions affected
- 2
Next human step
Resolved on July 22 with schema v3.1. The two affected submissions were re-mapped by hand.
INC-2026-0022LowResolved
Duplicate acknowledgements from the delivery service
A retry sent a second acknowledgement for 19 packages. No duplicate claims were created downstream.
- System
- Delivery service
- Owner
- Platform
- Opened
- July 11, 2026
- Submissions affected
- 19
Next human step
Resolved on July 12. Retries are now keyed on the submission reference.