workflow error:Invalid context structure: dify_model_identity='dify__file'

[laoxiaokang]

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.7.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

This is normal
but：

this is error

What should I do?

✔️ Expected Behavior

Can upload pictures and answer normally

❌ Actual Behavior

No response

[laoxiaokang]

@crazywoola I need your help o(╥﹏╥)o

[dosubot]

This error usually means the workflow is passing image/file data in a format the LLM node doesn't expect. For Dify 1.7.1, the LLM node with vision enabled needs files provided as an array of objects, each with required fields like type, id, transfer_method, filename, extension, and mime_type. Missing or mismatched fields will trigger the "Invalid context structure" error.

Here’s what you can check and try:

• Make sure your workflow payload for images includes all required fields. For example:

  {
    "type": "IMAGE",
    "id": "<file_id>",
    "transfer_method": "LOCAL_FILE",
    "filename": "example.jpg",
    "extension": "jpg",
    "mime_type": "image/jpeg"
  }

• In Docker, set FILES_URL to your host IP and port (not localhost), and set MULTIMODAL_SEND_IMAGE_FORMAT to url in your environment.
• After changing node input settings, publish updates for each node in the workflow editor.
• If you can't upgrade, use an HTTP request node to fetch the image by its original URL and pass the resulting file (with all metadata) to the next node.

If you still see errors, upgrading to a newer Dify version is recommended, as strict backend validation and incomplete payload propagation are known issues in older releases. More details and troubleshooting steps are discussed here and here.

To reply, just mention @dosu.

---

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