The 'Document Extractor' node failed to recognize the PDF file.

[Datawuxingding]

Self Checks

• I have read the Contributing Guide and Language Policy.
• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report, otherwise it will be closed.
• 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
• Please do not modify this template :) and fill in all the required fields.

Dify version

1.13.0

Cloud or Self Hosted

Cloud

Steps to reproduce

The 'Document Extractor' node failed to recognize the PDF file.

✔️ Expected Behavior

The 'Document Extractor' node sucess to recognize the word file.

❌ Actual Behavior

No response

[dosubot]

There have been several recent fixes to the Document Extractor node that address PDF extraction failures. A few things to check:

1. Variable handling issue: In v1.13.0, there's a reported bug where Document Extractor output variables are not accessible in certain node types within workflows [1]. This could make it appear that extraction failed when it's actually a variable propagation issue.

2. File input validation: Recent fixes (PRs fix: fix allow handle value is none #33031, refactor(api): add null safety to extractor_processor and firecrawl #35209) addressed cases where None or empty file lists passed to the Document Extractor caused crashes rather than graceful failures [2] [3]. Make sure the file variable being passed to the Document Extractor is properly populated.

3. PDF file integrity: The underlying PDF parser (pypdfium2) will fail on corrupted or non-standard PDF files [4]. You could try with a different PDF to rule this out.

Could you share:

• The error message or output you're seeing when extraction fails (the "Actual Behavior")?
• Whether this is intermittent or happens with all PDF files?
• Whether the same PDF worked previously on an earlier version?

This would help narrow down whether it's a file-specific issue, a variable passing issue, or something else.

Written by @dosu, approved by crazywoola

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[luochen211]

I traced this to the workflow Document Extractor implementation in graphon, which Dify consumes for this node. The current PDF path uses pypdfium2 only, so when PDFium returns an empty/whitespace text result the node succeeds with text: "" instead of trying another parser.

I opened a fix in Graphon that keeps PDFium as the primary parser and falls back to pypdf only when PDFium extracts no text:

• fix(document-extractor): add PDF text fallback graphon#189

Once that is merged and released, Dify can pick it up by bumping the graphon dependency.

[luochen211]

I also opened a Dify-side compatibility PR that installs a PDF fallback while the upstream Graphon fix is pending: #37525

[Datawuxingding]

There have been several recent fixes to the Document Extractor node that address PDF extraction failures. A few things to check:

1. Variable handling issue: In v1.13.0, there's a reported bug where Document Extractor output variables are not accessible in certain node types within workflows [1]. This could make it appear that extraction failed when it's actually a variable propagation issue.
2. File input validation: Recent fixes (PRs fix: fix allow handle value is none #33031, refactor(api): add null safety to extractor_processor and firecrawl #35209) addressed cases where None or empty file lists passed to the Document Extractor caused crashes rather than graceful failures [2] [3]. Make sure the file variable being passed to the Document Extractor is properly populated.
3. PDF file integrity: The underlying PDF parser (pypdfium2) will fail on corrupted or non-standard PDF files [4]. You could try with a different PDF to rule this out.

Could you share:

• The error message or output you're seeing when extraction fails (the "Actual Behavior")?
• Whether this is intermittent or happens with all PDF files?
• Whether the same PDF worked previously on an earlier version?

This would help narrow down whether it's a file-specific issue, a variable passing issue, or something else.

Written by @dosu, approved by crazywoola

To reply, just mention @dosu.

Docs are dead. Just use Dosu.

[Datawuxingding]

There have been several recent fixes to the Document Extractor node that address PDF extraction failures. A few things to check:

1. Variable handling issue: In v1.13.0, there's a reported bug where Document Extractor output variables are not accessible in certain node types within workflows [1]. This could make it appear that extraction failed when it's actually a variable propagation issue.
2. File input validation: Recent fixes (PRs fix: fix allow handle value is none #33031, refactor(api): add null safety to extractor_processor and firecrawl #35209) addressed cases where None or empty file lists passed to the Document Extractor caused crashes rather than graceful failures [2] [3]. Make sure the file variable being passed to the Document Extractor is properly populated.
3. PDF file integrity: The underlying PDF parser (pypdfium2) will fail on corrupted or non-standard PDF files [4]. You could try with a different PDF to rule this out.

Could you share:

• The error message or output you're seeing when extraction fails (the "Actual Behavior")?
• Whether this is intermittent or happens with all PDF files?
• Whether the same PDF worked previously on an earlier version?

This would help narrow down whether it's a file-specific issue, a variable passing issue, or something else.

Written by @dosu, approved by crazywoola

To reply, just mention @dosu.

Docs are dead. Just use Dosu.

1，
1.1, Input:
{
"variable_selector": [
"1771925400270",
"item"
]
}
1.2, Data processing:
{
"documents": [
{
"dify_model_identity": "dify__file",
"extension": ".pdf",
"filename": "YYT 1496-2016 红光治疗设备.pdf",
"id": null,
"mime_type": "application/pdf",
"related_id": "ffe977fb-7f40-4a13-9247-c86558fb28ce",
"remote_url": "https://d1n8dyg2n7hmf9.cloudfront.net:443/files/ffe977fb-7f40-4a13-9247-c86558fb28ce/file-preview?timestamp=1781659513&nonce=0e32bff9df29461dee7d73da53b768d4&sign=GD1D77VG6JPlnpXk0zRC_IbycrDwn_zoe2YcxFd49BQ%3D",
"size": 2226243,
"tenant_id": "33cd7dd0-d22d-4397-a5c1-3a023eb29494",
"transfer_method": "local_file",
"type": "document",
"url": "https://d1n8dyg2n7hmf9.cloudfront.net:443/files/ffe977fb-7f40-6558fb28ce/file-preview?timestamp=1781659518&nonce=2fe52a29e3fe766466&sign=IRNDJb6xsKRVkVFSeo%3D"
}
]
}
1.3, return result:
{
"text": ""
}

2. This issue happens with all PDF files.