Due to the job getting disabled from repo inactivity, there is a 3 month backlog of data that needs to be processed. As this data is being worked through it looks like some of the jobs do all the processing, but the data isn't actually archived to S3. This is because the script that copies the data to S3 by default only looks back 20 days. This fix will see the option being added to the github action to look back 3 months.
Once the backlog is sorted out can disable this option.
Due to the job getting disabled from repo inactivity, there is a 3 month backlog of data that needs to be processed. As this data is being worked through it looks like some of the jobs do all the processing, but the data isn't actually archived to S3. This is because the script that copies the data to S3 by default only looks back 20 days. This fix will see the option being added to the github action to look back 3 months.
Once the backlog is sorted out can disable this option.