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

The documentation of the application parameter retrieval interface is inconsistent with the returned values. #21795

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

Originally created by @liaokaime on GitHub (Jan 20, 2026).

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

Cloud or Self Hosted

Cloud

Steps to reproduce

Official Document A:
Image

Official Document B:
Image

The actual return of the interface：
Image

My settings：
Image

✔️ Expected Behavior

file_upload return the content according to Document A or Document B.

❌ Actual Behavior

The contents of Document A and Document B do not match the actual return.

Originally created by @liaokaime on GitHub (Jan 20, 2026). ### 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 1.11.4 ### Cloud or Self Hosted Cloud ### Steps to reproduce Official Document A: <img width="1104" height="2120" alt="Image" src="https://github.com/user-attachments/assets/4899f275-acb7-4cc8-84e4-ae2249549f97" /> Official Document B: <img width="1355" height="1606" alt="Image" src="https://github.com/user-attachments/assets/9a39f358-16da-49c5-acbe-2acade062401" /> The actual return of the interface： <img width="1131" height="742" alt="Image" src="https://github.com/user-attachments/assets/5179a82b-b623-4294-b0cd-236166b33820" /> My settings： <img width="1437" height="1104" alt="Image" src="https://github.com/user-attachments/assets/9424d3df-6e7c-415f-92f7-6e13b86c5452" /> ### ✔️ Expected Behavior `file_upload` return the content according to Document A or Document B. ### ❌ Actual Behavior The contents of Document A and Document B do not match the actual return.
yindo added the 📚 documentationstale labels 2026-02-21 20:14:20 -05:00
yindo commented 2026-02-21 20:14:20 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 20, 2026):

The inconsistency you’re seeing is because the API response for file_upload is generated directly from your app’s configuration (the features_dict), not from a fixed schema. The backend logic (specifically, the FileUploadConfigManager.convert method) builds the response based on fields like enabled, allowed_file_upload_methods, number_limits, and optionally image.detail. If your app’s configuration doesn’t match what’s shown in the documentation, the API response won’t match either. This means the documentation is currently out of sync with the actual implementation, and the structure/field names in the docs may not reflect what the API returns in practice. Recent code and config changes confirm this behavior and show that the default config matches what you’re seeing in the response, not the docs [source] [source].

If you need the API response to match the documentation, you’ll need to ensure your app’s configuration includes all the expected fields and values. Otherwise, the best next step is for maintainers to update the documentation to reflect the actual API output or clarify which config fields drive the response.

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 (Jan 20, 2026): <!-- Answer --> The inconsistency you’re seeing is because the API response for `file_upload` is generated directly from your app’s configuration (the `features_dict`), not from a fixed schema. The backend logic (specifically, the `FileUploadConfigManager.convert` method) builds the response based on fields like `enabled`, `allowed_file_upload_methods`, `number_limits`, and optionally `image.detail`. If your app’s configuration doesn’t match what’s shown in the documentation, the API response won’t match either. This means the documentation is currently out of sync with the actual implementation, and the structure/field names in the docs may not reflect what the API returns in practice. Recent code and config changes confirm this behavior and show that the default config matches what you’re seeing in the response, not the docs [[source]](https://github.com/langgenius/dify/blob/54921844bb3471303c91a2ed4cb5bd7140336053/api/core/app/app_config/features/file_upload/manager.py#L10-L29) [[source]](https://github.com/langgenius/dify/pull/30717). If you need the API response to match the documentation, you’ll need to ensure your app’s configuration includes all the expected fields and values. Otherwise, the best next step is for maintainers to update the documentation to reflect the actual API output or clarify which config fields drive the response. <!-- 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/e33ba968-68db-4553-83ec-0ec1ed7196a5?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/e33ba968-68db-4553-83ec-0ec1ed7196a5?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/e33ba968-68db-4553-83ec-0ec1ed7196a5?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/e33ba968-68db-4553-83ec-0ec1ed7196a5?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/e33ba968-68db-4553-83ec-0ec1ed7196a5?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/e33ba968-68db-4553-83ec-0ec1ed7196a5?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/e33ba968-68db-4553-83ec-0ec1ed7196a5?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%20inconsistency%20you%E2%80%99re%20seeing%20is%20because%20the%20API%20response%20for%20%60file_upload%60%20is%20generated%20directly%20from%20your%20app%E2%80%99s%20configuration%20%28the%20%60features_dict%60%29%2C%20not%20from%20a%20fixed%20schema.%20The%20backend%20logic%20%28specifically%2C%20the%20%60FileUploadConfigManager.convert%60%20method%29%20builds%20the%20response%20based%20on%20fields%20like%20%60enabled%60%2C%20%60allowed_file_upload_methods%60%2C%20%60number_limits%60%2C%20and%20optionally%20%60image.detail%60.%20If%20your%20app%E2%80%99s%20configuration%20doesn%E2%80%99t%20match%20what%E2%80%99s%20shown%20in%20the%20documentation%2C%20the%20API%20response%20won%E2%80%99t%20match%20either.%20This%20means%20the%20documentation%20is%20currently%20out%20of%20sync%20with%20the%20actual%20implementation%2C%20and%20the%20structure/field%20names%20in%20the%20docs%20may%20not%20reflect%20what%20the%20API%20returns%20in%20practice.%20Recent%20code%20and%20config%20changes%20confirm%20this%20behavior%20and%20show%20that%20the%20default%20config%20matches%20what%20you%E2%80%99re%20seeing%20in%20the%20response%2C%20not%20the%20docs%20%5B%5Bsource%5D%5D%28https%3A//github.com/langgenius/dify/blob/54921844bb3471303c91a2ed4cb5bd7140336053/api/core/app/app_config/features/file_upload/manager.py%23L10-L29%29%20%5B%5Bsource%5D%5D%28https%3A//github.com/langgenius/dify/pull/30717%29.%0A%0AIf%20you%20need%20the%20API%20response%20to%20match%20the%20documentation%2C%20you%E2%80%99ll%20need%20to%20ensure%20your%20app%E2%80%99s%20configuration%20includes%20all%20the%20expected%20fields%20and%20values.%20Otherwise%2C%20the%20best%20next%20step%20is%20for%20maintainers%20to%20update%20the%20documentation%20to%20reflect%20the%20actual%20API%20output%20or%20clarify%20which%20config%20fields%20drive%20the%20response.)&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/31294)
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 stale 📚 documentation
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#21795
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?