Alberto Islas

Correct, I'll add the new upload type and we'll only accept the uploads and store the files.

@ERosendo the new `UPLOAD_TYPE` for this new upload type is: `BASE_CASE_QUERY_ADVANCED = 14` More details at https://github.com/freelawproject/courtlistener/pull/2418 Please let me know if you have any questions.

Yeah, I've checked this. I checked some of the recent errors from today on sentry and seems that the pages that are arriving to this [upload type](https://www.courtlistener.com/api/rest/v3/recap/?upload_type=12&status!=2) `CASE_QUERY_PAGE = 12`...

Sure, I'll give it a look and see what's happening.

I checked the errors on sentry related to this issue. Seems that we still continue receiving a few `CASE_QUERY_RESULT_PAGE = 14` uploads as `CASE_QUERY_PAGE = 12` and also there are...

I checked briefly this error, seems that the problem is that the received file is a district docket that mentions the same case (same title: USA v. BANKMAN-FRIED) multiple times...

Sure, here are some examples extracted from S3 after checking the related `ProcessingQueues`. These two are from `cod`, we've had hundreds, if not thousands, of errors and processing queues for...

Additionally, there were some events that were triggered. However, after checking all possible sources through which a docket can be updated (RSS, RECAP Email, Docket reports, Case query pages, RECAP...

Thanks for your answers. > It feels a bit weird to be looking at data issues in this way though. Shouldn't we be able to just push whatever is in...

Great! I've created the 3 Juriscraper issues, related to this one. https://github.com/freelawproject/juriscraper/issues/846 https://github.com/freelawproject/juriscraper/issues/845 https://github.com/freelawproject/juriscraper/issues/844 @grossir let me know if you have any questions. I'll work on checking the field tracker...