langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-19 16:44:00 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

After uploading Word, the text extractor node reported an error message stating 'Variable ['1763719894377', 'files'] is not an ArrayFileEgg' #20612

New Issue
Closed
opened 2026-02-21 20:08:09 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 20:08:09 -05:00
Owner
Copy Link
Copy Source

Originally created by @libin1219 on GitHub (Nov 27, 2025).

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

0.10.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image Image

✔️ Expected Behavior

The text extractor should parse and extract Word content

❌ Actual Behavior

Variable ['1763719894377', 'files'] is not an ArrayFileSegment

Originally created by @libin1219 on GitHub (Nov 27, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.10.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce <img width="1149" height="881" alt="Image" src="https://github.com/user-attachments/assets/5545f3d0-3c77-40c3-9efe-ba9ce00649cb" /> <img width="1620" height="815" alt="Image" src="https://github.com/user-attachments/assets/c7d3f5f9-d755-4664-bf72-25fb5b50816e" /> ### ✔️ Expected Behavior The text extractor should parse and extract Word content ### ❌ Actual Behavior Variable ['1763719894377', 'files'] is not an ArrayFileSegment
yindo closed this issue 2026-02-21 20:08:09 -05:00
yindo commented 2026-02-21 20:08:09 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 27, 2025):

The error means the text extractor node expects its input to be an ArrayFileSegment (an array of File objects), but it's receiving something else—often a plain list of dictionaries or incorrectly mapped file metadata. This strict type check is enforced in the backend: if the variable isn't an ArrayFileSegment or FileSegment, extraction fails immediately (see code).

To fix this, make sure your workflow passes files as actual File objects, not just JSON blobs or dicts. The most common causes are: the upstream node outputs a list of dicts instead of File objects, or the variable mapping between nodes is off (details).

Checklist:

  • The input to the extractor must be an array of File objects (ArrayFileSegment), not just file metadata.
  • If you’re building the workflow JSON manually or using a plugin, ensure the file variable is mapped and serialized correctly.
  • If you’re stuck, try a minimal workflow: create a new workflow that takes a file as input and outputs the same file, and set the file type as “other” with the extension explicitly set (like .doc or .docx) (workaround).
  • If you’re using a plugin, make sure the actual file content is present in the blob attribute, not just a URL or metadata (plugin tip).

Recent updates have improved file input handling, so if you’re able to upgrade, newer versions may handle these cases more gracefully (PR #26848).

If you need to debug further, inspect the actual value passed to the extractor node—if it’s not an ArrayFileSegment of File objects, adjust the upstream node or mapping accordingly.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Nov 27, 2025): <!-- Answer --> The error means the text extractor node expects its input to be an ArrayFileSegment (an array of File objects), but it's receiving something else—often a plain list of dictionaries or incorrectly mapped file metadata. This strict type check is enforced in the backend: if the variable isn't an ArrayFileSegment or FileSegment, extraction fails immediately [(see code)](https://github.com/langgenius/dify/blob/5f2e0d63474c843b285ad586b98d88f4bc94fe60/api/core/workflow/nodes/document_extractor/node.py#L53-L425). To fix this, make sure your workflow passes files as actual File objects, not just JSON blobs or dicts. The most common causes are: the upstream node outputs a list of dicts instead of File objects, or the variable mapping between nodes is off [(details)](https://github.com/langgenius/dify/blob/5f2e0d63474c843b285ad586b98d88f4bc94fe60/api/core/workflow/runtime/variable_pool.py#L80-L241). Checklist: - The input to the extractor must be an array of File objects (ArrayFileSegment), not just file metadata. - If you’re building the workflow JSON manually or using a plugin, ensure the file variable is mapped and serialized correctly. - If you’re stuck, try a minimal workflow: create a new workflow that takes a file as input and outputs the same file, and set the file type as “other” with the extension explicitly set (like `.doc` or `.docx`) [(workaround)](https://github.com/langgenius/dify-official-plugins/issues/835). - If you’re using a plugin, make sure the actual file content is present in the `blob` attribute, not just a URL or metadata [(plugin tip)](https://github.com/langgenius/dify-official-plugins/issues/1857). Recent updates have improved file input handling, so if you’re able to upgrade, newer versions may handle these cases more gracefully [(PR #26848)](https://github.com/langgenius/dify/pull/26848). If you need to debug further, inspect the actual value passed to the extractor node—if it’s not an ArrayFileSegment of File objects, adjust the upstream node or mapping accordingly. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/9a9d5fb7-6e5c-43ae-9182-996f383cae9f?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/9a9d5fb7-6e5c-43ae-9182-996f383cae9f?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/9a9d5fb7-6e5c-43ae-9182-996f383cae9f?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/9a9d5fb7-6e5c-43ae-9182-996f383cae9f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/9a9d5fb7-6e5c-43ae-9182-996f383cae9f?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/9a9d5fb7-6e5c-43ae-9182-996f383cae9f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/9a9d5fb7-6e5c-43ae-9182-996f383cae9f?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=The%20error%20means%20the%20text%20extractor%20node%20expects%20its%20input%20to%20be%20an%20ArrayFileSegment%20%28an%20array%20of%20File%20objects%29%2C%20but%20it%27s%20receiving%20something%20else%E2%80%94often%20a%20plain%20list%20of%20dictionaries%20or%20incorrectly%20mapped%20file%20metadata.%20This%20strict%20type%20check%20is%20enforced%20in%20the%20backend%3A%20if%20the%20variable%20isn%27t%20an%20ArrayFileSegment%20or%20FileSegment%2C%20extraction%20fails%20immediately%20%5B%28see%20code%29%5D%28https%3A//github.com/langgenius/dify/blob/5f2e0d63474c843b285ad586b98d88f4bc94fe60/api/core/workflow/nodes/document_extractor/node.py%23L53-L425%29.%0A%0ATo%20fix%20this%2C%20make%20sure%20your%20workflow%20passes%20files%20as%20actual%20File%20objects%2C%20not%20just%20JSON%20blobs%20or%20dicts.%20The%20most%20common%20causes%20are%3A%20the%20upstream%20node%20outputs%20a%20list%20of%20dicts%20instead%20of%20File%20objects%2C%20or%20the%20variable%20mapping%20between%20nodes%20is%20off%20%5B%28details%29%5D%28https%3A//github.com/langgenius/dify/blob/5f2e0d63474c843b285ad586b98d88f4bc94fe60/api/core/workflow/runtime/variable_pool.py%23L80-L241%29.%20%0A%0AChecklist%3A%0A-%20The%20input%20to%20the%20extractor%20must%20be%20an%20array%20of%20File%20objects%20%28ArrayFileSegment%29%2C%20not%20just%20file%20metadata.%0A-%20If%20you%E2%80%99re%20building%20the%20workflow%20JSON%20manually%20or%20using%20a%20plugin%2C%20ensure%20the%20file%20variable%20is%20mapped%20and%20serialized%20correctly.%0A-%20If%20you%E2%80%99re%20stuck%2C%20try%20a%20minimal%20workflow%3A%20create%20a%20new%20workflow%20that%20takes%20a%20file%20as%20input%20and%20outputs%20the%20same%20file%2C%20and%20set%20the%20file%20type%20as%20%E2%80%9Cother%E2%80%9D%20with%20the%20extension%20explicitly%20set%20%28like%20%60.doc%60%20or%20%60.docx%60%29%20%5B%28workaround%29%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/835%29.%0A-%20If%20you%E2%80%99re%20using%20a%20plugin%2C%20make%20sure%20the%20actual%20file%20content%20is%20present%20in%20the%20%60blob%60%20attribute%2C%20not%20just%20a%20URL%20or%20metadata%20%5B%28plugin%20tip%29%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/1857%29.%0A%0ARecent%20updates%20have%20improved%20file%20input%20handling%2C%20so%20if%20you%E2%80%99re%20able%20to%20upgrade%2C%20newer%20versions%20may%20handle%20these%20cases%20more%20gracefully%20%5B%28PR%20%2326848%29%5D%28https%3A//github.com/langgenius/dify/pull/26848%29.%0A%0AIf%20you%20need%20to%20debug%20further%2C%20inspect%20the%20actual%20value%20passed%20to%20the%20extractor%20node%E2%80%94if%20it%E2%80%99s%20not%20an%20ArrayFileSegment%20of%20File%20objects%2C%20adjust%20the%20upstream%20node%20or%20mapping%20accordingly.)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/28788)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#20612
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?