dify - 💡(How to fix) Fix Title: [1.14.0] API file upload is broken, works fine in 1.13.0 [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
langgenius/dify#35764Fetched 2026-05-02 05:47:07
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
1
Participants
Timeline (top)
labeled ×1
RAW_BUFFERClick to expand / collapse

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

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  1. Create a workflow with a file input field.
  2. Upload a valid file and get the file_id.
  3. Call POST /v1/workflows/run with valid inputs.
  4. Always get 400: { "code": "invalid_param", "message": "Invalid upload file" }

✔️ Expected Behavior

The file upload API should work normally and return 200.

❌ Actual Behavior

When calling POST /v1/workflows/run with a valid file input, the API returns: Status: 400 Body: { "code": "invalid_param", "message": "Invalid upload file", "status": 400 }

My request body: { "inputs": { "shangchuan": { "transfer_method": "local_file", "upload_file_id": "e135c086-f517-49d6-aad3-dd951c815caf", "type": "document" }, "requirement": "总结" }, "response_mode": "blocking", "user": "rongjie" }

All file IDs are valid and uploaded via /v1/files/upload correctly. All parameter formats (object / string file ID) have been tested and all fail in 1.14.

Expected Behavior

The API should accept the file parameter and execute the workflow successfully, just like in Dify 1.13.

extent analysis

TL;DR

The issue can be resolved by investigating the file upload handling in the POST /v1/workflows/run endpoint, specifically focusing on the upload_file_id parameter.

Guidance

  • Verify that the upload_file_id is correctly retrieved and passed in the request body, ensuring it matches the format expected by the API.
  • Check the server-side logs for any errors or warnings related to file upload handling, which may indicate the root cause of the invalid_param error.
  • Test the POST /v1/files/upload endpoint separately to confirm that file uploads are successful and the returned file_id is valid.
  • Compare the implementation of file upload handling between Dify 1.13 and 1.14 to identify any changes that may be causing the issue.

Example

No code snippet is provided as the issue is more related to API interaction and parameter handling.

Notes

The issue seems to be specific to Dify 1.14, and the fact that all parameter formats have been tested and failed suggests a potential regression or change in the API's behavior.

Recommendation

Apply workaround: Investigate and adjust the file upload handling in the POST /v1/workflows/run endpoint to ensure compatibility with Dify 1.14, as the issue seems to be related to a change in the API's behavior.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING