Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reprocess recap_emailprocessingqueue rows with INVALID_CONTENT status #4890

Open
grossir opened this issue Jan 6, 2025 · 1 comment
Open

Comments

@grossir
Copy link
Contributor

grossir commented Jan 6, 2025

Some old recap_emailprocessingqueue rows have status_message "Not a valid notification email. No message content.", and status 6 ("INVALID_CONTENT").

This was triggered because we couldn't parse data out of the email (see code below). However, when manually testing some old emails on currenct code, we wouldn't trigger the condition.

report = S3NotificationEmail(map_cl_to_pacer_id(epq.court_id))
report._parse_text(body)
data = report.data
if (
data == {}
or len(data["dockets"]) == 0
or len(data["dockets"][0]["docket_entries"]) == 0
or data["dockets"][0]["docket_entries"][0]["pacer_case_id"] is None
):
msg = "Not a valid notification email. No message content."
async_to_sync(mark_pq_status)(
epq, msg, PROCESSING_STATUS.INVALID_CONTENT, "status_message"
)

I was looking at emails from bankruptcy courts. For example, this email from cacb. The case on CL

Data that would be parsed:

{'court_id': 'cacb',
 'appellate': False,
 'dockets': [{'case_name': 'Ayse Necla Necar',
   'docket_number': '8:22-bk-11711',
   'date_filed': None,
   'docket_entries': [{'date_filed': datetime.date(2022, 10, 5),
     'description': 'Chapter 7 Voluntary Petition for Individuals . Fee Amount $338 Filed by Ayse Necla Necar Statement of Intention for Individuals Filing Under Chapter 7 (Form 108) due 11/4/2022. Summary of Assets and Liabilities (Form 106Sum or 206Sum ) due 10/19/2022. Schedule A/B: Property (Form 106A/B or 206A/B) due 10/19/2022. Schedule C: The Property You Claim as Exempt (Form 106C) due 10/19/2022. Schedule D: Creditors Who Have Claims Secured by Property (Form 106D or 206D) due 10/19/2022. Schedule E/F: Creditors Who Have Unsecured Claims (Form 106E/F or 206E/F) due 10/19/2022. Schedule G: Executory Contracts and Unexpired Leases (Form 106G or 206G) due 10/19/2022. Schedule H: Your Codebtors (Form 106H or 206H) due 10/19/2022. Schedule I: Your Income (Form 106I) due 10/19/2022. Schedule J: Your Expenses (Form 106J) due 10/19/2022. Declaration Under Penalty of Perjury for Non-Individual Debtors (Form 202) due 10/19/2022. Statement of Financial Affairs (Form 107 or 207) due 10/19/2022. Chapter 7 Statement of Your Current Monthly Income (Form 122A-1) Due: 10/19/2022. Statement of Exemption from Presumption of Abuse (Form 122A-1Supp) Due: 10/19/2022. Chapter 7 Means Test Calculation (Form 122A-2) Due: 10/19/2022. Incomplete Filings due by 10/19/2022. (Heston, Benjamin)',
     'short_description': 'Voluntary Petition (Chapter 7)',
     'document_url': 'https://ecf.cacb.uscourts.gov/doc1/9730105877663?pdf_header=&magic_num=76185394&de_seq_num=2&caseid=1952572',
     'document_number': '1',
     'pacer_doc_id': '9730105877663',
     'pacer_case_id': '1952572',
     'pacer_seq_no': '2',
     'pacer_magic_num': '76185394'}],
   'federal_dn_office_code': '8',
   'federal_dn_case_type': 'bk',
   'federal_dn_judge_initials_assigned': None,
   'federal_dn_judge_initials_referred': None,
   'federal_defendant_number': None}],
 'contains_attachments': False,
 'email_recipients': [{'name': '',
   'email_addresses': ['[email protected]',
    '...',
    '[email protected]']}]}

Which would add at least the DocketEntry.description to the current DocketEntry

@grossir grossir changed the title Reprocess INVALID_CONTENT recap_emailprocessingqueue rows Reprocess recap_emailprocessingqueue rows with INVALID_CONTENT status Jan 6, 2025
@mlissner
Copy link
Member

mlissner commented Jan 7, 2025

Hm. How many of these are there and how much time do you think it would take to reprocess them? Not sure it's worth the effort, but maybe!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants