[BUG] cancelled task still polling

[He-Pin]

You can see, when I clicked the cancel button ,the request is failed, but the task is still polling

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔍 Additional Context

Summary

Based on web search results, I found relevant patterns and context for your issue about cancelled tasks still polling. Here's the key information:

Core Problem Pattern

The pattern you're experiencing is documented in similar issues where polling continues despite cancellation requests, indicating that the dispatcher or task handler did not properly cancel its polling tasks.

Common Root Causes

1. Bare Exception Handlers: A common cause is when bare except statements hide CancelledError exceptions, preventing the polling loop from properly exiting when cancellation is requested.

2. Cooperative Cancellation Requirement: Cancellation is cooperative - code must be provided a CancellationToken and must do something with that token in order to be cancelable.

3. Polling Without Proper Checks: Tasks must periodically check cancellation status within loops - the polling code should include checks like cancellationToken.ThrowIfCancellationRequested() or if (ct.IsCancellationRequested) before running task steps.

Key Implementation Patterns

Polling requires code that periodically reads the cancellation status property and uses the ThrowIfCancellationRequested method to check the property and throw the exception.

Recommended Solution Approach

When a cancellation request comes in, set the task status to "Cancelling", and before running each task step, check if the task status was changed to cancelling.

---

Note: While the issue description is brief, the search results reveal this is a well-documented pattern across multiple frameworks (aiogram, Redux-Saga, AWS SDK, etc.). To provide more specific guidance for your implementation, it would be helpful to know:

• What technology/framework is being used
• The specific cancellation mechanism (button click, timeout, etc.)
• How the polling loop is currently structured

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!

[dosubot]

Hi @He-Pin! I'm Dosu and I’m helping the inspector team.

This is a known issue: cancelling a task does not immediately stop polling because the polling logic is tied to the task's status, not the cancel action itself. The polling continues as long as there are active (non-terminal) tasks, and only stops when all tasks are complete or the user disables auto-refresh. If the cancel request fails, polling will still continue until the server reports the task as terminal. This behavior is confirmed in recent issues and is related to recent changes in the polling and cancellation logic (#1108, #1105, PR #1094).

The relevant code is in the TasksTab component, where polling is managed by a useEffect with setInterval, and cancellation is handled by handleCancelTask, which only refreshes the task list but does not stop polling (TasksTab.tsx). To address this, consider updating the polling logic to disable auto-refresh or clear the polling interval when a cancel attempt is made, regardless of its outcome.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

  

[matteo8p]

@He-Pin We have auto-polling on by default when you're on the Tasks tab. You can use the switch to turn off autopolling.

[He-Pin]

when the task is been canceled, the current auto polling is still.polling