Abort button in the Execution page

[LarsEbt]

Feature Description

Add an "Abort" / "Stop" button to the Agent Executions page for runs that are still active (running state).

Right now, when an execution is triggered via the API and ends up in a loop or keeps running unexpectedly, there is no straightforward way to stop it from the Executions UI. The only option is a complicated manual workaround to abort the run, which is error-prone and slow.

Proposed behavior:

• Show a clearly visible Abort button on any execution that is still in a "running" / active state, both in the executions list and in the execution detail view.
• Clicking it should immediately cancel the ongoing run and mark the execution as stopped/aborted.
• Ideally also expose an equivalent endpoint via the API so runs started through the API can be aborted programmatically as well.

This would prevent runaway executions (e.g. infinite loops) from continuing and racking up unnecessary token/compute costs.

Feature Category

UI/UX Improvement

Problem Statement

When a flow is triggered via the API and gets stuck in a loop or keeps running, there is currently no easy way to stop the active execution from the Executions page. Aborting it manually is complicated and takes time, during which the run keeps consuming tokens and generating avoidable costs. There is no direct "stop this run" control for active executions.

Proposed Solution

Add an "Abort" button directly in the Agent Executions page for any run that is currently in the running state (the run already has a running indicator/icon, so it can be detected reliably).

Specifics:

• Place the Abort button in the executions list row (next to the running status icon) and also in the execution detail view.
• Only show it while the execution is active; once the run finishes, fails, or is aborted, the button disappears or becomes disabled.
• Clicking it cancels the ongoing run immediately and updates the status to "Aborted" / "Stopped".
• Expose a matching API endpoint (e.g. POST to abort an execution by its ID) so runs started via the API can also be cancelled programmatically.

Mockups or References

No response

Additional Context

No response

[HaoBinGuan]

Hi, I'd like to work on this issue.I did a quick initial code read and found that Flowise already has an AbortControllerPool and existing abort handling for running flows.Before opening a PR, I'd like to confirm the preferred direction:- should this be implemented as a new endpoint like POST /executions/:id/abort?- should the abort action reuse the existing ${chatflowId}_${chatId} abort controller key, using the execution's agentflowId and sessionId?- should the UI show the Abort button only for executions in the INPROGRESS state?If this approach sounds reasonable, I can start with a small PR that adds the backend abort endpoint and the Abort button in the Agent Executions list/detail view.

[Abhiiishek44]

Hi, I’d like to work on this issue.

I noticed there may already be some work started, but I don’t see any linked PR yet. Could you please confirm if anyone is actively working on it?

Thanks!