Describe the bug
When terminating the stream output, clicking the stop button frequently leads to the stream continuing to render and print. Upon investigation, it was discovered that the EDT (Event Dispatch Thread) is unable to clear historical tasks, causing the consumption endpoint (EDT) to continue processing historical tasks even after the associated upstream delivery endpoint has been shut down. This behavior creates the impression among users that the system cannot be properly terminated.

We propose implementing a mechanism on the EDT consumer side to monitor whether the current latest sessionId matches the sessionId embedded in the historical stream (the historical stream should carry the sessionId status). In the event of any inconsistency, the token can be proactively discarded. This approach may effectively achieve immediate cessation of the stream upon closure.