The "cancel run" button for switching sessions and returning to the previous session after the playground task runs is missing and cannot be cancelled

[chendalian]

What happened?

Describe the bug
A clear and concise description of what the bug is.
If it is a question or suggestion, please use Discussions
instead.

To Reproduce
Steps to reproduce the behavior. Please include code and outputs such as stacktrace.

• If your input is just "I tried X, and it didn't work" or
  "X is not working", your issue will be ignored.
• If your input is not well formatted, it will hurt readability and
  may be ignored as well.

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Which packages was the bug in?

AutoGen Studio (autogensudio)

AutoGen library version.

Python dev (main branch)

Other library version.

No response

Model used

No response

Model provider

None

Other model provider

No response

Python version

None

.NET version

None

Operating system

None

[victordibia]

Hi @chendalian ,

Thanks for this. The general implementation at the moment is that each time a task is run, there is a "session" managed by a socket connection - this is how agent updates are streamed to the UI. When the user navigates away from that page/session, connection is closed which in turn ends the task currently.

Were you looking more towards tasks that run in the background and can be monitored or cancelled? Can you discuss the use case in a bit more detail?

[chendalian]

Hi @chendalian ,  你好

Thanks for this. The general implementation at the moment is that each time a task is run, there is a "session" managed by a socket connection - this is how agent updates are streamed to the UI. When the user navigates away from that page/session, connection is closed which in turn ends the task currently.谢谢你。目前的一般实现是，每次运行任务时，都有一个由套接字连接管理的“会话”——这就是代理更新流式传输到 UI 的方式。当用户离开该页面/会话时，连接将关闭，进而结束当前任务。

Were you looking more towards tasks that run in the background and can be monitored or cancelled? Can you discuss the use case in a bit more detail?您是否更关注在后台运行并且可以监控或取消的任务？您能否更详细地讨论一下用例？

According to the implementation you described, when Task 1 is running and switches to other task 2, Task 1 will stop and not continue to output. When the currently deployed main branch switches, if you switch back to Task 1, the task is still ongoing, and if you wait for a moment, there will be output.
Some tasks take a long time to run and other tasks may run in the middle. So, would it be better if the other running tasks continue to run in the background when switching tasks and can be cancelled? According to the current situation, it is a single task running, and users must wait for this task to finish running