Stuck Appeals

tags: Caseflow Data

Stuck AMA appeals

Echo: Investigation: Discover any AMA appeal states that won't move forward automatically #14307

Ticket origin: Distribution Tasks were cancelled, but they had other trees open

Cancelled Distribution Tasks #119

We believe these were affected by a bug we corrected last year.

AC 2: Discover any potential orphan path in our codebase

Requires understanding "Task code flow"

Initial thoughts:

  • examining the codebase is like trying to hit a moving target. Bugs can be introduced at any time, so we would have to continually redo this AC with any relevant code change.
  • I have some initial work that examines the ordering of task creation to identify patterns (and anomalies) from actual task trees. Including updates to tasks would be a big lift that involves examining PaperTrail logs.
  • Is there a way to extract a task-based state machine from the code?
  • Manual code analysis:
    • identify code that creates, closes, and puts on-hold tasks
    • enumerate all the triggers and hooks related to tasks
    • Then ensure there is always a state machine path to move the appeal forward

TODO: Pull out this interpretation of AC 2 into a separate ticket.

Correct interpretation of AC 2: Explain why appeals from AC 1 got to this bad state

IHP kickoff

Capture when 1 task activates another task

2 reasons an IHP task is not created:

  1. POA not associated with AMA Appeal
  2. Legacy Appeal
Select a repo