{"version":"2.1.271","anchor":"pdf-page-count-detection-now-distinguishes-failure-reasons-a","canonical_anchor":"pdf-page-count-detection-now-distinguishes-failure-reasons-a","heading":"PDF page-count detection now distinguishes failure reasons and handles unknown-length PDFs","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/pdf-page-count-detection-now-distinguishes-failure-reasons-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### PDF page-count detection now distinguishes failure reasons and handles unknown-length PDFs\n\nPDF page-count detection now reports specific failure reasons and handles PDFs with an unknown page count\n\n**What**\n\nA new internal step for running `pdfinfo` (the tool used to determine a PDF's page count) now reports a structured reason when it fails \u2014 timeout, not_found, nonzero_exit, no_exit_status, or no_page_count \u2014 instead of just returning nothing. When this happens, the PDF is not attached, and Claude is told to use the Read tool's `pages` parameter to read it in parts, without being told a page count that isn't actually known.\n\n**Why**\n\nThis avoids Claude being given a wrong or fabricated page count for a PDF whose length couldn't be determined, and steers it toward reading the file in parts instead.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}