langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-22 12:36:14 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

conversations delete api response and documentation are different #6247

New Issue
Closed
opened 2026-02-21 18:14:43 -05:00 by yindo · 4 comments
yindo commented 2026-02-21 18:14:43 -05:00
Owner
Copy Link
Copy Source

Originally created by @good2luck on GitHub (Oct 22, 2024).

Originally assigned to: @crazywoola on GitHub.

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

0.8.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I used Docker for private deployment and found that the response did not meet expectations when deleting conversations through API calls。

at the same time，i saw this commit：https://github.com/langgenius/dify/pull/767/files，but it didn't work

image

✔️ Expected Behavior

return ：
{
"result": "success"
}

❌ Actual Behavior

return：
{
"id": null,
"name": null,
"inputs": null,
"status": null,
"introduction": null,
"created_at": null
}

Originally created by @good2luck on GitHub (Oct 22, 2024). Originally assigned to: @crazywoola on GitHub. ### 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 0.8.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I used Docker for private deployment and found that the response did not meet expectations when deleting conversations through API calls。 at the same time，i saw this commit：https://github.com/langgenius/dify/pull/767/files，but it didn't work ![image](https://github.com/user-attachments/assets/6af9d32e-8278-48ab-af87-dc9972e81ade) ### ✔️ Expected Behavior return ： { "result": "success" } ### ❌ Actual Behavior return： { "id": null, "name": null, "inputs": null, "status": null, "introduction": null, "created_at": null }
yindo added the 🐞 bug📚 documentation labels 2026-02-21 18:14:43 -05:00
yindo closed this issue 2026-02-21 18:14:43 -05:00
yindo commented 2026-02-21 18:14:44 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 22, 2024):

Hey @good2luck! I'm here to assist you with any bugs, questions, or contributions you have for the Dify project. Let's work together to resolve this issue!

There is a known discrepancy between the expected and actual response formats for the DELETE conversation API in Dify. The expected response format, as per the documentation, should be:

{"result": "success"}, 204

However, the actual implementation in the codebase returns a success message with a 200 status code, and it seems like you are receiving a response with null fields instead of the expected success message [1].

There is no specific information available about recent changes or commits that address this discrepancy in the DELETE conversation API response. The pull request #767 you mentioned seems to address documentation issues but does not resolve the response format issue you are experiencing.

To address this, you might want to check if there are any configuration settings in your self-hosted Docker setup that could affect the API response. Additionally, reviewing the implementation of the DELETE conversation API in the codebase might provide insights into why null fields are being returned [2][1].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Oct 22, 2024): <!-- Greeting --> Hey @good2luck! I'm here to assist you with any bugs, questions, or contributions you have for the Dify project. Let's work together to resolve this issue! <!-- Answer --> There is a known discrepancy between the expected and actual response formats for the DELETE conversation API in Dify. The expected response format, as per the documentation, should be: ```json {"result": "success"}, 204 ``` However, the actual implementation in the codebase returns a success message with a 200 status code, and it seems like you are receiving a response with null fields instead of the expected success message <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/controllers/web/conversation.py)</sup>. There is no specific information available about recent changes or commits that address this discrepancy in the DELETE conversation API response. The pull request #767 you mentioned seems to address documentation issues but does not resolve the response format issue you are experiencing. To address this, you might want to check if there are any configuration settings in your self-hosted Docker setup that could affect the API response. Additionally, reviewing the implementation of the DELETE conversation API in the codebase might provide insights into why null fields are being returned <sup>[[2]](https://github.com/langgenius/dify/blob/main/sdks/python-client/dify_client/client.py)</sup><sup>[[1]](https://github.com/langgenius/dify/blob/main/api/controllers/web/conversation.py)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:14:44 -05:00
Author
Owner
Copy Link
Copy Source

@good2luck commented on GitHub (Oct 23, 2024):

Who can look this problem

@good2luck commented on GitHub (Oct 23, 2024): Who can look this problem
yindo commented 2026-02-21 18:14:44 -05:00
Author
Owner
Copy Link
Copy Source

@Yusaney commented on GitHub (Oct 23, 2024):

I have the same issue. I get the same response:

{
  "id": null,
  "name": null,
  "inputs": null,
  "status": null,
  "introduction": null,
  "created_at": null
}

and the conversations are not being deleted.

@Yusaney commented on GitHub (Oct 23, 2024): I have the same issue. I get the same response: ``` { "id": null, "name": null, "inputs": null, "status": null, "introduction": null, "created_at": null } ``` and the conversations are not being deleted.
yindo commented 2026-02-21 18:14:44 -05:00
Author
Owner
Copy Link
Copy Source

@BenjaminX commented on GitHub (Nov 1, 2024):

Reproduce, review code inspection this issue and Rename API the same issue.
It is recommended that the rename API be called when a new session is created and the first conversation is completed.

@crazywoola reassign issus to me?

@BenjaminX commented on GitHub (Nov 1, 2024): Reproduce, review code inspection this issue and Rename API the same issue. It is recommended that the rename API be called when a new session is created and the first conversation is completed. @crazywoola reassign issus to me?
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 📚 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#6247
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?