Discover and correct improperly undispatched appeals

[lomky]

Description

Reopening a dispatched AMA case is a nontrivial effort that involves external dependencies. We now have a process for doing this. In the process of researching we came across some cases that had been previously 'undispatched' with only the task tree adjusted. This ticket is to discover those appeals and correct their state so they can properly flow

Acceptance criteria

• Previously undispatched cases are in a healthy state that will flow through bva dispatch again

Background/context/resources

Known cases:
Known case,
Known case

Slack convo

Technical notes

Good starting points:

• Metabase query for appeals that aren't dispatched with a poa_participant_id
• Bat team docs
• searching slack BatTeam channel

Bat team: How to undispatch a case
Properly undispatched case with research dive

[hschallhorn]

what is this chart?

1 | 
2 | 
3 | |||||||||
5 | |||
8 | 

Look for cases without completed dispatch tasks (or dispatch tasks still open?) that have "outcoded" markers

• appeal has poa_participant_id set, appeal has efectuations or decision_document but isn't done

Why 3?

• Probably have to ask for approvals/confirmation or at least notify BVA.
• Two different cases of unknown state. These cases could have possibly progressed though caseflow, further deviating from the expected state

Why 5?

• (Hopefully not) other cases could be in this state. May need to file follow up ticket to handle any others identified.
• Kat just did this, it was pretty non-trivial, but this has a boost of the existing docs

[GabbyTISTA]

Moved to https://vajira.max.gov/browse/CASEFLOW-1621