获取会话历史消息 api: v1/messages 网页发的消息 api查不到 #12537

Closed
opened 2026-02-21 19:07:52 -05:00 by yindo · 4 comments
Owner

Originally created by @alexhmyang on GitHub (Apr 3, 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

latest

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

获取会话历史消息 api: v1/messages 网页发的消息 api查不到

✔️ Expected Behavior

No response

Actual Behavior

No response

Originally created by @alexhmyang on GitHub (Apr 3, 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 latest ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 获取会话历史消息 api: v1/messages 网页发的消息 api查不到 ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug🤔 cant-reproduce labels 2026-02-21 19:07:52 -05:00
yindo closed this issue 2026-02-21 19:07:52 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Apr 3, 2025):

嗨 @alexhmyang!我是一个可以帮助你解决bug、回答问题并成为贡献者的机器人。在你等待人类维护者的同时,我会尽力帮助你。期待一起解决问题!🤖

I found two similar discussions that might be relevant to your issue:

  1. Conversation history cannot be retrieved - This discussion is still open and might contain insights related to retrieving conversation history [1].

  2. DIY API interface call, unable to parse context - This discussion is also open and addresses issues with API calls and context parsing, which might be related to your problem [2].

You might find useful information or potential solutions in these threads.

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 (Apr 3, 2025): <!-- Greeting --> 嗨 @alexhmyang!我是一个可以帮助你解决bug、回答问题并成为贡献者的机器人。在你等待人类维护者的同时,我会尽力帮助你。期待一起解决问题!🤖 <!-- Answer --> I found two similar discussions that might be relevant to your issue: 1. [Conversation history cannot be retrieved](https://github.com/langgenius/dify/discussions/11000) - This discussion is still open and might contain insights related to retrieving conversation history <sup>[[1]](https://github.com/langgenius/dify/discussions/11000)</sup>. 2. [DIY API interface call, unable to parse context](https://github.com/langgenius/dify/discussions/10044) - This discussion is also open and addresses issues with API calls and context parsing, which might be related to your problem <sup>[[2]](https://github.com/langgenius/dify/discussions/10044)</sup>. You might find useful information or potential solutions in these threads. <!-- 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/ee49ee57-df40-4a9c-9ebb-c03298a7c88d?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/ee49ee57-df40-4a9c-9ebb-c03298a7c88d?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/ee49ee57-df40-4a9c-9ebb-c03298a7c88d?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/ee49ee57-df40-4a9c-9ebb-c03298a7c88d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ee49ee57-df40-4a9c-9ebb-c03298a7c88d?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/ee49ee57-df40-4a9c-9ebb-c03298a7c88d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ee49ee57-df40-4a9c-9ebb-c03298a7c88d?feedback_type=other)</sup>
Author
Owner

@teamen commented on GitHub (Apr 18, 2025):

获取历史对话 报错

{
    "message": "Internal Server Error",
    "code": "unknown"
}
@teamen commented on GitHub (Apr 18, 2025): 获取历史对话 报错 ``` { "message": "Internal Server Error", "code": "unknown" } ```
Author
Owner

@teamen commented on GitHub (Apr 18, 2025):

Why close this issue? The API /messages respond the unknown error:

{
    "message": "Internal Server Error",
    "code": "unknown"
}
@teamen commented on GitHub (Apr 18, 2025): Why close this issue? The API /messages respond the unknown error: ``` { "message": "Internal Server Error", "code": "unknown" } ```
Author
Owner

@shanafilan commented on GitHub (May 15, 2025):

hello,请问你解决这个问题了吗

@shanafilan commented on GitHub (May 15, 2025): hello,请问你解决这个问题了吗
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#12537