dify - 💡(How to fix) Fix chatflows that are manually stopped by the user remain in a running state in the log system [4 comments, 2 participants]

TL;DR

The issue can be mitigated by ensuring proper state updates in the conversation logs when an agent's response is stopped.

Guidance

• Investigate the backend logging system to identify why the conversation log entry remains in a "running" state after the agent's response is stopped.
• Verify that the state update logic is correctly implemented to transition the conversation state to "stop" when the agent's response is interrupted.
• Check the token usage calculation to ensure it accurately reflects the consumption after an interrupted session.
• Review the logging system's data consistency to prevent discrepancies between the actual state and the displayed state.

Example

No code snippet can be provided without more context, but the fix likely involves updating the state transition logic in the conversation log entry.

Notes

The issue seems to be related to the state management and logging in the backend system. Without more information about the system's architecture and code, it's challenging to provide a precise solution.

Recommendation

Apply a workaround by manually updating the conversation log entry state to "stop" when an agent's response is interrupted, until the root cause is identified and fixed.