langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-22 01:55:27 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

THE LMM VISUAL ERROR,I USE qwen-vl-plus-2025-01-25 #447

New Issue
Closed
opened 2026-02-16 10:19:26 -05:00 by yindo · 3 comments
yindo commented 2026-02-16 10:19:26 -05:00
Owner
Copy Link
Copy Source

Originally created by @chenhunhun on GitHub (Jul 14, 2025).

Self Checks

  • 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 (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1,4.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Run failed: Invalid context structure: dify_model_identity='dify__file' id=None tenant_id='0dad44c0-a051-455b-bfc7-f56700534e3c' type=<FileType.IMAGE: 'image'> transfer_method=<FileTransferMethod.LOCAL_FILE: 'local_file'> remote_url='/files/7df4aab9-4264-4d5f-bb94-9957b7361a29/file-preview?timestamp=1752506410&nonce=3baf399f5d444bff631fd8337de59845&sign=zo4Ro6JbhqPQI5zgi0vRPYMxUox2hHNm8Of8oJ_bUlo=' related_id='7df4aab9-4264-4d5f-bb94-9957b7361a29' filename='CTRIP2.png' extension='.png' mime_type='image/png' size=24957

✔️ Expected Behavior

I HOPE TO GET THE PIC IMAGE 'S INFO

❌ Actual Behavior

No response

Originally created by @chenhunhun on GitHub (Jul 14, 2025). ### Self Checks - [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 (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1,4.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Run failed: Invalid context structure: dify_model_identity='dify__file' id=None tenant_id='0dad44c0-a051-455b-bfc7-f56700534e3c' type=<FileType.IMAGE: 'image'> transfer_method=<FileTransferMethod.LOCAL_FILE: 'local_file'> remote_url='/files/7df4aab9-4264-4d5f-bb94-9957b7361a29/file-preview?timestamp=1752506410&nonce=3baf399f5d444bff631fd8337de59845&sign=zo4Ro6JbhqPQI5zgi0vRPYMxUox2hHNm8Of8oJ_bUlo=' related_id='7df4aab9-4264-4d5f-bb94-9957b7361a29' filename='CTRIP2.png' extension='.png' mime_type='image/png' size=24957 ### ✔️ Expected Behavior I HOPE TO GET THE PIC IMAGE 'S INFO ### ❌ Actual Behavior _No response_
yindo closed this issue 2026-02-16 10:19:26 -05:00
yindo commented 2026-02-16 10:19:27 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jul 14, 2025):

The "Invalid context structure" error with qwen-vl-plus in Dify usually means the image/file input isn't matching the strict format the backend expects. Dify enforces a specific schema for multimodal models—if the image context (like file metadata, URL, or type) is missing required fields or isn't structured exactly as needed, you'll get this error. This can happen if the file variable isn't set as an Array[File], if the file URL is missing a scheme (should be http:// or https://), or if the model integration expects a different context shape than what your workflow provides. There are also known issues with context validation and structured outputs in self-hosted Dify 1.4.2 that may not be patched yet in Docker deployments [source 1] [source 2].

For similar errors, users have fixed the problem by making sure the file variable is set as Array[File] in the workflow, and in some cases, by modifying the ArrayFileVariable class in the codebase to inherit from ArrayVariable, then restarting the Docker container [source 3]. Also, not all models support direct file/image input—OpenAI, Claude, and Gemini are confirmed, but qwen-vl-plus support is less clear [source 4].

Check that your image input matches the expected schema, the file variable is set correctly, and the file URL is valid. If you recently upgraded or changed your workflow, make sure all nodes and variables are updated to match the new requirements. If the issue persists, it may be due to a missing patch in your self-hosted version.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (Jul 14, 2025): <!-- Answer --> The "Invalid context structure" error with qwen-vl-plus in Dify usually means the image/file input isn't matching the strict format the backend expects. Dify enforces a specific schema for multimodal models—if the image context (like file metadata, URL, or type) is missing required fields or isn't structured exactly as needed, you'll get this error. This can happen if the file variable isn't set as an `Array[File]`, if the file URL is missing a scheme (should be `http://` or `https://`), or if the model integration expects a different context shape than what your workflow provides. There are also known issues with context validation and structured outputs in self-hosted Dify 1.4.2 that may not be patched yet in Docker deployments [[source 1]](https://github.com/langgenius/dify/issues/16502) [[source 2]](https://github.com/langgenius/dify/issues/12048). For similar errors, users have fixed the problem by making sure the file variable is set as `Array[File]` in the workflow, and in some cases, by modifying the `ArrayFileVariable` class in the codebase to inherit from `ArrayVariable`, then restarting the Docker container [[source 3]](https://github.com/langgenius/dify/issues/12048). Also, not all models support direct file/image input—OpenAI, Claude, and Gemini are confirmed, but qwen-vl-plus support is less clear [[source 4]](https://github.com/langgenius/dify/issues/16502). Check that your image input matches the expected schema, the file variable is set correctly, and the file URL is valid. If you recently upgraded or changed your workflow, make sure all nodes and variables are updated to match the new requirements. If the issue persists, it may be due to a missing patch in your self-hosted version. <!-- 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/1ad34272-40df-4af0-8da5-584bb1ae0dbe?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/1ad34272-40df-4af0-8da5-584bb1ae0dbe?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/1ad34272-40df-4af0-8da5-584bb1ae0dbe?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/1ad34272-40df-4af0-8da5-584bb1ae0dbe?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/1ad34272-40df-4af0-8da5-584bb1ae0dbe?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/1ad34272-40df-4af0-8da5-584bb1ae0dbe?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/1ad34272-40df-4af0-8da5-584bb1ae0dbe?feedback_type=other)</sup>&nbsp;&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/22374)
yindo commented 2026-02-16 10:19:27 -05:00
Author
Owner
Copy Link
Copy Source

@hjlarry commented on GitHub (Jul 15, 2025):

try to config the env variable FILES_URL

@hjlarry commented on GitHub (Jul 15, 2025): try to config the env variable `FILES_URL`
yindo commented 2026-02-16 10:19:27 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 20, 2025):

Hi, @chenhunhun. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported an "Invalid context structure" error when using qwen-vl-plus-2025-01-25 with Dify 1.4.2 self-hosted via Docker.
  • The error was due to the image/file input not matching Dify's strict expected schema, such as missing file metadata or incorrect file variable type.
  • I suggested fixes including setting the file variable as Array[File], validating file URLs, updating workflow nodes, and configuring the FILES_URL environment variable.
  • Known unpatched issues exist in Dify 1.4.2 Docker deployments that may contribute to this problem.

What's Next:

  • Please confirm if this issue is still relevant with the latest version of the dify-official-plugins repository by commenting here.
  • If no further updates are provided, I will automatically close this issue in 5 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Aug 20, 2025): Hi, @chenhunhun. I'm [Dosu](https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported an "Invalid context structure" error when using qwen-vl-plus-2025-01-25 with Dify 1.4.2 self-hosted via Docker. - The error was due to the image/file input not matching Dify's strict expected schema, such as missing file metadata or incorrect file variable type. - I suggested fixes including setting the file variable as `Array[File]`, validating file URLs, updating workflow nodes, and configuring the `FILES_URL` environment variable. - Known unpatched issues exist in Dify 1.4.2 Docker deployments that may contribute to this problem. **What's Next:** - Please confirm if this issue is still relevant with the latest version of the dify-official-plugins repository by commenting here. - If no further updates are provided, I will automatically close this issue in 5 days. Thank you for your understanding and contribution!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
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-official-plugins#447
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?