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

对话记录名称无法正确保存，都是为New conversation【The conversation record name cannot be saved correctly, and is always New conversation】 #8670

New Issue
Closed
opened 2026-02-21 18:26:56 -05:00 by yindo · 6 comments
yindo commented 2026-02-21 18:26:56 -05:00
Owner
Copy Link
Copy Source

Originally created by @wubucheng on GitHub (Feb 26, 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

master

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

已经配置了中文，但是当每次对话时不会显示正确的提问信息作为对话历史名称，都固定了New conversation。查看检测与日志发现都是New conversation
The conversation record name cannot be saved correctly, and is always New conversation

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @wubucheng on GitHub (Feb 26, 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 master ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 已经配置了中文，但是当每次对话时不会显示正确的提问信息作为对话历史名称，都固定了New conversation。查看检测与日志发现都是New conversation The conversation record name cannot be saved correctly, and is always New conversation ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 18:26:56 -05:00
yindo closed this issue 2026-02-21 18:26:56 -05:00
yindo commented 2026-02-21 18:26:57 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 26, 2025):

Hey @wubucheng! 👋 I'm here to help you with bugs, answer questions, and even guide you on contributing. Let's tackle this together!

I found some similar threads related to the issue of conversation names not being saved correctly and defaulting to "New conversation":

  1. An open issue suggests updating to version 0.6.16, which should resolve issues related to conversation name generation. It also recommends using the API /conversations/:conversation_id/name instead of relying on the auto_generate_name parameter, as it may be deprecated in the future [1].

  2. Another open discussion suggests customizing or modifying the default conversation title by setting the title auto-generation to false and then using the conversation rename API. By setting auto_generate to true, you can achieve asynchronous title generation [2].

These solutions might help address the problem you're experiencing with conversation names not being saved correctly.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Feb 26, 2025): <!-- Greeting --> Hey @wubucheng! 👋 I'm here to help you with bugs, answer questions, and even guide you on contributing. Let's tackle this together! <!-- Answer --> I found some similar threads related to the issue of conversation names not being saved correctly and defaulting to "New conversation": 1. An open issue suggests updating to version 0.6.16, which should resolve issues related to conversation name generation. It also recommends using the API `/conversations/:conversation_id/name` instead of relying on the `auto_generate_name` parameter, as it may be deprecated in the future <sup>[[1]](https://github.com/langgenius/dify/issues/13653)</sup>. 2. Another open discussion suggests customizing or modifying the default conversation title by setting the title auto-generation to `false` and then using the conversation rename API. By setting `auto_generate` to `true`, you can achieve asynchronous title generation <sup>[[2]](https://github.com/langgenius/dify/discussions/14323)</sup>. These solutions might help address the problem you're experiencing with conversation names not being saved correctly. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/2910f493-4680-45cc-85a7-95dfb2762c20?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/2910f493-4680-45cc-85a7-95dfb2762c20?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/2910f493-4680-45cc-85a7-95dfb2762c20?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/2910f493-4680-45cc-85a7-95dfb2762c20?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/2910f493-4680-45cc-85a7-95dfb2762c20?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/2910f493-4680-45cc-85a7-95dfb2762c20?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/2910f493-4680-45cc-85a7-95dfb2762c20?feedback_type=other)</sup>
yindo commented 2026-02-21 18:26:57 -05:00
Author
Owner
Copy Link
Copy Source

@wubucheng commented on GitHub (Feb 26, 2025):

@dosu 版本已经更新了，今天拉取最新的官方镜像。我是用官方docker镜像运行的，难道需要以源码部署的方式运行？

@wubucheng commented on GitHub (Feb 26, 2025): @dosu 版本已经更新了，今天拉取最新的官方镜像。我是用官方docker镜像运行的，难道需要以源码部署的方式运行？
yindo commented 2026-02-21 18:26:57 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 26, 2025):

使用官方 Docker 镜像运行 Dify 应该不需要切换到源码部署方式。确保您已经正确配置了 .env 文件和 docker-compose-template.yaml 文件中的相关设置。您可以检查以下几点：

  1. 确保 .env 文件中设置了所有必要的环境变量，特别是与超时相关的变量 [1]。
  2. 确保 docker-compose-template.yaml 文件中的服务定义和配置正确无误 [2]。
  3. 检查是否有任何已知的 Docker 镜像相关问题，尽管目前没有找到具体的已知问题 [3]。

如果这些都没有问题，您可以尝试使用对话重命名 API 来手动设置对话名称，避免依赖自动生成功能 [4]。

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Feb 26, 2025): <!-- Answer --> 使用官方 Docker 镜像运行 Dify 应该不需要切换到源码部署方式。确保您已经正确配置了 `.env` 文件和 `docker-compose-template.yaml` 文件中的相关设置。您可以检查以下几点： 1. 确保 `.env` 文件中设置了所有必要的环境变量，特别是与超时相关的变量 <sup>[[1]](https://github.com/langgenius/dify/issues/12880)</sup>。 2. 确保 `docker-compose-template.yaml` 文件中的服务定义和配置正确无误 <sup>[[2]](https://github.com/langgenius/dify/blob/main/docker/docker-compose-template.yaml)</sup>。 3. 检查是否有任何已知的 Docker 镜像相关问题，尽管目前没有找到具体的已知问题 <sup>[[3]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/llms.txt)</sup>。 如果这些都没有问题，您可以尝试使用对话重命名 API 来手动设置对话名称，避免依赖自动生成功能 <sup>[[4]](https://github.com/langgenius/dify/blob/main/api/controllers/service_api/app/conversation.py)</sup>。 <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/95db3ef6-e04c-47d6-a7b4-1028e94666d5?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/95db3ef6-e04c-47d6-a7b4-1028e94666d5?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/95db3ef6-e04c-47d6-a7b4-1028e94666d5?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/95db3ef6-e04c-47d6-a7b4-1028e94666d5?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/95db3ef6-e04c-47d6-a7b4-1028e94666d5?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/95db3ef6-e04c-47d6-a7b4-1028e94666d5?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/95db3ef6-e04c-47d6-a7b4-1028e94666d5?feedback_type=other)</sup>
yindo commented 2026-02-21 18:26:57 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 26, 2025):

Close due to #1542

@crazywoola commented on GitHub (Feb 26, 2025): Close due to #1542
yindo commented 2026-02-21 18:26:57 -05:00
Author
Owner
Copy Link
Copy Source

@MrWangChong commented on GitHub (Feb 26, 2025):

@dosu 在哪里设置可以设置auto_generate为true？

@MrWangChong commented on GitHub (Feb 26, 2025): @dosu 在哪里设置可以设置auto_generate为true？
yindo commented 2026-02-21 18:26:57 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 26, 2025):

您可以在向 /conversations/:conversation_id/name 端点发送 POST 请求时，将 auto_generate 设置为 true。以下是使用 cURL 的示例：

curl -X POST '${props.appDetail.api_base_url}/conversations/{conversation_id}/name' \
--header 'Authorization: Bearer {api_key}' \
--header 'Content-Type: application/json' \
--data-raw '{
    "name": "",
    "auto_generate": true,
    "user": "abc-123"
}'

这样可以实现自动生成对话名称 [1]。

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Feb 26, 2025): <!-- Answer --> 您可以在向 `/conversations/:conversation_id/name` 端点发送 POST 请求时，将 `auto_generate` 设置为 `true`。以下是使用 cURL 的示例： ```bash curl -X POST '${props.appDetail.api_base_url}/conversations/{conversation_id}/name' \ --header 'Authorization: Bearer {api_key}' \ --header 'Content-Type: application/json' \ --data-raw '{ "name": "", "auto_generate": true, "user": "abc-123" }' ``` 这样可以实现自动生成对话名称 <sup>[[1]](https://github.com/langgenius/dify/blob/main/web/app/components/develop/template/template_chat.zh.mdx)</sup>。 <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/04f805f8-0f51-4e80-8ee7-a26d47a3db2f?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/04f805f8-0f51-4e80-8ee7-a26d47a3db2f?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/04f805f8-0f51-4e80-8ee7-a26d47a3db2f?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/04f805f8-0f51-4e80-8ee7-a26d47a3db2f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/04f805f8-0f51-4e80-8ee7-a26d47a3db2f?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/04f805f8-0f51-4e80-8ee7-a26d47a3db2f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/04f805f8-0f51-4e80-8ee7-a26d47a3db2f?feedback_type=other)</sup>
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
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#8670
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?