openclaw - 💡(How to fix) Fix Dashboard: No Stop button when message is queued [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#52686Fetched 2026-04-08 01:20:22
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
0
Author
Timeline (top)
commented ×1

When sending a message to an agent in the Dashboard, if the message enters a queued state (e.g., due to API concurrency limits), there is no visible Stop button to cancel or interrupt the queued/running task.

Root Cause

When sending a message to an agent in the Dashboard, if the message enters a queued state (e.g., due to API concurrency limits), there is no visible Stop button to cancel or interrupt the queued/running task.

RAW_BUFFERClick to expand / collapse

Description

When sending a message to an agent in the Dashboard, if the message enters a queued state (e.g., due to API concurrency limits), there is no visible Stop button to cancel or interrupt the queued/running task.

Steps to Reproduce

  1. Open OpenClaw Dashboard (http://127.0.0.1:18789/)
  2. Send a message to an agent
  3. While the agent is processing (or queued), observe the UI
  4. No Stop/Cancel button is visible

Expected Behavior

A Stop button (e.g., red square icon) should appear while a message is being processed or queued, allowing the user to cancel the operation.

Environment

  • OpenClaw version: 2026.3.13
  • Node.js: v22.22.0
  • macOS: 26.3
  • Gateway: running, RPC ok
  • Browser: Safari / Chrome (WebView in app)

Additional Context

Gateway status is healthy (RPC probe: ok, Runtime: running). The issue appears to be a frontend/Dashboard UI problem, not a backend issue.

extent analysis

Fix Plan

To address the missing Stop button issue, we need to modify the frontend code to display the button when a message is in a queued or running state.

Code Changes

Here are the steps to implement the fix:

  • Modify the MessageSender component to track the message state:
// MessageSender.js
import React, { useState, useEffect } from 'react';

const MessageSender = () => {
  const [messageState, setMessageState] = useState('idle');

  useEffect(() => {
    // Update messageState when the message is sent
    const handleMessageSend = (state) => {
      setMessageState(state);
    };
    // ...
  }, []);

  return (
    <div>
      {messageState === 'queued' || messageState === 'running' ? (
        <button onClick={() => handleCancelMessage()}>Stop</button>
      ) : null}
      {/* ... */}
    </div>
  );
};
  • Implement the handleCancelMessage function to cancel the message:
// MessageSender.js
const handleCancelMessage = () => {
  // API call to cancel the message
  fetch('/api/cancel-message', {
    method: 'POST',
    headers: { 'Content-Type': 'application/json' },
    body: JSON.stringify({ messageId: messageId }),
  })
    .then((response) => response.json())
    .then((data) => {
      // Update messageState to 'cancelled'
      setMessageState('cancelled');
    })
    .catch((error) => console.error(error));
};

Verification

To verify the fix, follow these steps:

  • Send a message to an agent
  • While the agent is processing or queued, check if the Stop button is visible
  • Click the Stop button to cancel the message
  • Verify that the message is cancelled and the button disappears

Extra Tips

  • Make sure to update the API endpoint to handle the cancel message request.
  • Test the fix in different scenarios, such as when multiple messages are sent concurrently.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING