R3 DISP-S1 historical processing is now executed by a stand-alone CLI application as opposed to the batch_process lambda. batch_process lambda should now revert back to a state before the R3 logic was introduced:
Cleaner, easier maintenance, etc
The extra R3 code could trigger an edge-case bug in future. No reason to keep it around
That R3 code doesn't work anyway because the historical processing logic has changed significantly after it was written
Checked for duplicates
Yes - I've already checked
Alternatives considered
Yes - and alternatives don't suffice
Related problems
No response
Describe the feature request
R3 DISP-S1 historical processing is now executed by a stand-alone CLI application as opposed to the batch_process lambda. batch_process lambda should now revert back to a state before the R3 logic was introduced: