You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a result, the PQ receives a nullpacer_case_id and it is also missing in the parsed data. I'm not sure if there is a different way to obtain it from the extension side, or perhaps the pacer_doc_id (available), court (available), and docket number (which is not being parsed or received in the upload) from the attachment page could be used to search for the case and docket entry.
I checked some of the uploads related to this issue and found that the caseID is either blank or null in all the URLs within the upload, for example:
TransportRoom?servlet=ShowDoc&caseId=null&recapDocNum=1&recapCaseNum=20-15019&dls_id='+dls+'&caseId=
TransportRoom?servlet=ShowDocMulti&caseId=null&recapDocNum=1&recapCaseNum=20-15019&outputType=doc&d=11552967&outputForm=view&incPdfFooter=
As a result, the PQ receives a
null
pacer_case_id
and it is also missing in the parsed data. I'm not sure if there is a different way to obtain it from the extension side, or perhaps thepacer_doc_id
(available), court (available), and docket number (which is not being parsed or received in the upload) from the attachment page could be used to search for the case and docket entry.Sentry Issue: COURTLISTENER-5T3
Filed by: @albertisfu
The text was updated successfully, but these errors were encountered: