You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
Pleas do not modify this template :) and fill in all the required fields.
Dify version
0.6.0-fix1
Cloud or Self Hosted
Cloud, Self Hosted (Docker)
Steps to reproduce
After the workflow is released, if create a new conversation and switch applications,
find that the original conversation has not been saved, resulting in an error in sending messages.
✔️ Expected Behavior
No response
❌ Actual Behavior
No response
The text was updated successfully, but these errors were encountered:
Hey @DayoWang, great to see you around here again! Hope you're doing well amidst these tech puzzles.
Based on the information you've provided, it seems like the issue you're experiencing might be related to the WorkflowEventTriggerCallback class in the Dify codebase. This class is designed to handle various events related to workflow execution and individual workflow node execution. It's responsible for publishing different types of events to a queue system during the lifecycle of a workflow and its nodes.
One of the methods in this class, on_node_text_chunk, is supposed to handle the publishing of text chunks, which could be part of the workflow conversations. However, as shown in the provided code snippet, the on_node_text_chunk method has a pass statement, indicating that the method does not perform any operation. This lack of implementation means that any attempt to handle or save workflow conversations by invoking this method would result in no action being taken, which could lead to errors or the inability to save conversations when the workflow is released and the application context is switched.
To resolve this issue, the on_node_text_chunk method needs to be properly implemented to handle the publishing of text chunks as part of the workflow conversations. However, as I'm unable to create pull requests or issues, I would recommend reaching out to the repository maintainers or contributors to address this issue.
You can find more details about the WorkflowEventTriggerCallback class and its methods in the Dify repository.
I hope this information helps! If you have any other questions or need further clarification, feel free to ask.
Self Checks
Dify version
0.6.0-fix1
Cloud or Self Hosted
Cloud, Self Hosted (Docker)
Steps to reproduce
After the workflow is released, if create a new conversation and switch applications,
find that the original conversation has not been saved, resulting in an error in sending messages.
✔️ Expected Behavior
No response
❌ Actual Behavior
No response
The text was updated successfully, but these errors were encountered: