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

Feedback api set content parameter, but useless #15218

New Issue
Closed
opened 2026-02-21 19:20:44 -05:00 by yindo · 4 comments
yindo commented 2026-02-21 19:20:44 -05:00
Owner
Copy Link
Copy Source

Originally created by @SuperZhanggy on GitHub (Jul 9, 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.5.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

feedback api set content parameter is useless

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @SuperZhanggy on GitHub (Jul 9, 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.5.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce feedback api set content parameter is useless ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug🙏 help wanted labels 2026-02-21 19:20:44 -05:00
yindo closed this issue 2026-02-21 19:20:44 -05:00
yindo commented 2026-02-21 19:20:44 -05:00
Author
Owner
Copy Link
Copy Source

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

The feedback API does store the content parameter in the database, but most API responses and the admin/console UI do not expose this field by design. If you want to retrieve feedback content, you can use the service API endpoint GET /v1/app/feedbacks with your app's API token—this endpoint returns all feedbacks for your app, including the content field, because it serializes the full feedback object from the database. Other endpoints (like single-message feedback fetch or the web UI) do not include content in their responses, which is why it appears "useless" even though it is saved internally see code reference.

If you need the content field exposed elsewhere, you would need to modify the relevant field serializers (for example, add content to feedback_fields in the API code). This limitation is intentional, likely for privacy or UX reasons.

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 9, 2025): <!-- Answer --> The feedback API does store the content parameter in the database, but most API responses and the admin/console UI do not expose this field by design. If you want to retrieve feedback content, you can use the service API endpoint GET `/v1/app/feedbacks` with your app's API token—this endpoint returns all feedbacks for your app, including the content field, because it serializes the full feedback object from the database. Other endpoints (like single-message feedback fetch or the web UI) do not include content in their responses, which is why it appears "useless" even though it is saved internally [see code reference](https://github.com/langgenius/dify/blob/4cb50f1809cb6c888d7177a6909d6738686a1e76/api/services/message_service.py). If you need the content field exposed elsewhere, you would need to modify the relevant field serializers (for example, add content to feedback_fields in the API code). This limitation is intentional, likely for privacy or UX reasons. <!-- 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/5111b831-d7f8-4346-abac-f2274372b79c?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/5111b831-d7f8-4346-abac-f2274372b79c?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/5111b831-d7f8-4346-abac-f2274372b79c?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/5111b831-d7f8-4346-abac-f2274372b79c?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/5111b831-d7f8-4346-abac-f2274372b79c?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/5111b831-d7f8-4346-abac-f2274372b79c?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/5111b831-d7f8-4346-abac-f2274372b79c?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/22099)
yindo commented 2026-02-21 19:20:44 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jul 9, 2025):

Please provide the full curl command.

@crazywoola commented on GitHub (Jul 9, 2025): Please provide the full curl command.
yindo commented 2026-02-21 19:20:44 -05:00
Author
Owner
Copy Link
Copy Source

@SuperZhanggy commented on GitHub (Jul 9, 2025):

Image 我这边用的python sdk ，data 中添加content 参数，请求成功后，message_feedbacks 表中content 字段Null 变成了空字符串

@SuperZhanggy commented on GitHub (Jul 9, 2025): <img width="1584" height="780" alt="Image" src="https://github.com/user-attachments/assets/0ac9ee8a-aede-47aa-8b7c-e9be35813f57" /> 我这边用的python sdk ，data 中添加content 参数，请求成功后，message_feedbacks 表中content 字段Null 变成了空字符串
yindo commented 2026-02-21 19:20:45 -05:00
Author
Owner
Copy Link
Copy Source

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

Hi, @SuperZhanggy. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Recap:

  • You reported that the feedback API's content parameter appears ineffective in Dify v1.5.1 (Docker), with the content field showing as empty in the message_feedbacks table after requests.
  • It was clarified that the content is indeed stored in the database but intentionally not exposed in most API responses or the admin UI.
  • To retrieve the feedback content, the GET /v1/app/feedbacks endpoint with the app's API token should be used.
  • This design choice is likely for privacy or user experience reasons and would require code changes to expose content elsewhere.
  • You provided additional context via a screenshot showing the issue with the Python SDK.

Next Steps:

  • Please confirm if this behavior is still relevant or problematic with the latest version of Dify.
  • If it is, feel free to comment here to keep the discussion open; otherwise, I will automatically close this issue in 15 days.

Thanks for your understanding and contribution!

@dosubot[bot] commented on GitHub (Aug 28, 2025): Hi, @SuperZhanggy. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Recap:** - You reported that the feedback API's content parameter appears ineffective in Dify v1.5.1 (Docker), with the content field showing as empty in the message_feedbacks table after requests. - It was clarified that the content is indeed stored in the database but intentionally not exposed in most API responses or the admin UI. - To retrieve the feedback content, the GET `/v1/app/feedbacks` endpoint with the app's API token should be used. - This design choice is likely for privacy or user experience reasons and would require code changes to expose content elsewhere. - You provided additional context via a screenshot showing the issue with the Python SDK. **Next Steps:** - Please confirm if this behavior is still relevant or problematic with the latest version of Dify. - If it is, feel free to comment here to keep the discussion open; otherwise, I will automatically close this issue in 15 days. Thanks for your understanding and contribution!
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 🐞 bug 🙏 help wanted
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#15218
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?