langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-21 17:45:23 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

OpenAI Compatible Dify App Extension with memory mode all messages makes the log unreadable (message count is only 1) and the conversation id is different at each interaction #445

New Issue
Closed
opened 2026-02-16 10:19:26 -05:00 by yindo · 3 comments
yindo commented 2026-02-16 10:19:26 -05:00
Owner
Copy Link
Copy Source

Originally created by @remisharrock on GitHub (Jul 12, 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 Dify issues & Dify Official Plugins, 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.6.0

Plugin version

0.0.6

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

call the endpoint multiple times with this extension with the memory mode "all messages".
The log is unreadable because each time there is an interaction there is a new line and a new conversation id is created.

Image

and when you click one log line you get the entire history in one shot:

Image

would it be possible to maintain the conversation id at each interaction to make the log readable (not many log lines but only ONE with all the interactions inside)

✔️ Error log

No response

Originally created by @remisharrock on GitHub (Jul 12, 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 [Dify issues](https://github.com/langgenius/dify/issues) & [Dify Official Plugins](https://github.com/langgenius/dify-official-plugins/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.6.0 ### Plugin version 0.0.6 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce call the endpoint multiple times with this extension with the memory mode "all messages". The log is unreadable because each time there is an interaction there is a new line and a new conversation id is created. <img width="1679" height="648" alt="Image" src="https://github.com/user-attachments/assets/dbdf85e0-ca4a-40cd-b819-6982034cb617" /> and when you click one log line you get the entire history in one shot: <img width="601" height="993" alt="Image" src="https://github.com/user-attachments/assets/2d23d8cf-46b8-4539-81ec-e71722fec969" /> would it be possible to maintain the conversation id at each interaction to make the log readable (not many log lines but only ONE with all the interactions inside) ### ✔️ Error log _No response_
yindo added the bug label 2026-02-16 10:19:26 -05:00
yindo closed this issue 2026-02-16 10:19:26 -05:00
yindo commented 2026-02-16 10:19:26 -05:00
Author
Owner
Copy Link
Copy Source

@hjlarry commented on GitHub (Jul 14, 2025):

The OpenAI API is stateless, so the key question is how to determine if it belongs to the same conversation.

@hjlarry commented on GitHub (Jul 14, 2025): The OpenAI API is stateless, so the key question is how to determine if it belongs to the same conversation.
yindo commented 2026-02-16 10:19:27 -05:00
Author
Owner
Copy Link
Copy Source

@remisharrock commented on GitHub (Jul 16, 2025):

Correct so what I did is the contrary, my use case is with Pipecat integration so what I did was creating a Pipecat Dify service and it works. Here is the code
https://github.com/pipecat-ai/pipecat/pull/378#issuecomment-3069815840

@remisharrock commented on GitHub (Jul 16, 2025): Correct so what I did is the contrary, my use case is with Pipecat integration so what I did was creating a Pipecat Dify service and it works. Here is the code https://github.com/pipecat-ai/pipecat/pull/378#issuecomment-3069815840
yindo commented 2026-02-16 10:19:27 -05:00
Author
Owner
Copy Link
Copy Source

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

Hi, @remisharrock. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported that the OpenAI Compatible Dify App Extension generates a new conversation ID for each interaction when memory mode is set to "all messages," leading to fragmented and unreadable logs.
  • The maintainer explained that the OpenAI API is stateless, which complicates maintaining consistent conversation IDs.
  • You shared a workaround using Pipecat integration that successfully keeps conversation continuity in logs.
  • The issue remains unresolved as there is no built-in solution yet to maintain a consistent conversation ID within the extension.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of the dify-official-plugins repository by commenting here.
  • If I do not hear back within 5 days, I will automatically close this issue.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Aug 20, 2025): Hi, @remisharrock. I'm [Dosu](https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported that the OpenAI Compatible Dify App Extension generates a new conversation ID for each interaction when memory mode is set to "all messages," leading to fragmented and unreadable logs. - The maintainer explained that the OpenAI API is stateless, which complicates maintaining consistent conversation IDs. - You shared a workaround using Pipecat integration that successfully keeps conversation continuity in logs. - The issue remains unresolved as there is no built-in solution yet to maintain a consistent conversation ID within the extension. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of the dify-official-plugins repository by commenting here. - If I do not hear back within 5 days, I will automatically close this issue. Thank you for your understanding and contribution!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
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-official-plugins#445
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?