Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Persistent [1] badge on Sessions icon after failed cron task is deleted

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…

Root Cause

  1. Create a scheduled task (e.g., a daily cron job at 9:00 AM) with delivery mode "announce"
  2. The task fails to deliver because no channel is configured (delivery fails silently)
  3. Delete or cancel the scheduled task via cron remove
  4. Observe: the "1" badge on the Sessions icon persists
RAW_BUFFERClick to expand / collapse

Bug Description

After a scheduled cron task fails to execute, a purple badge with a white "1" appears on the Sessions icon in the Control UI. Even after the failed task is subsequently deleted or cancelled, the badge remains indefinitely — through Gateway restarts and over multiple days.

Steps to Reproduce

  1. Create a scheduled task (e.g., a daily cron job at 9:00 AM) with delivery mode "announce"
  2. The task fails to deliver because no channel is configured (delivery fails silently)
  3. Delete or cancel the scheduled task via cron remove
  4. Observe: the "1" badge on the Sessions icon persists

Expected Behavior

  • When the failed task is deleted, the badge should disappear
  • The badge count should accurately reflect current failed/delivered tasks, not persist after the task is removed

Environment

  • OpenClaw version: 2026.5.7
  • Platform: macOS (Darwin 26.3, ARM64)
  • Gateway: local, running via LaunchAgent
  • openclaw status output: Tasks: 0 active · 0 queued · 3 issues · audit clean · 3 tracked
  • Sessions list shows 3 active sessions, but UI badge shows only "1"

Additional Context

  • Gateway restart does not clear the badge
  • The badge has persisted for several days
  • The badge appears on the Sessions icon specifically (not the Tasks icon)

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…
#latency issue#model loading#dependency error#configuration error#environment variable

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Persistent [1] badge on Sessions icon after failed cron task is deleted