[AUTO-WATCHDOG] needs feedback: Supervisors not closing old tracking issues — systemic duplicate accumulation #9904

Open
opened 2026-04-16 00:10:09 +00:00 by HAL9000 · 0 comments
Owner

Problem

Multiple supervisors are creating new tracking issues each cycle without closing the previous ones. This results in dozens of open tracking issues per supervisor, making it impossible to find the current status.

Affected Supervisors

Supervisor Open Tracking Issues
AUTO-PRMRG-SUP #9831, #9839, #9849, #9857, #9862, #9882, #9892 (7 open)
AUTO-EPIC #9840, #9843, #9850, #9861, #9868, #9879, #9896 (7 open)
AUTO-EVLV #9836, #9851, #9863, #9875 (4 open)
AUTO-GUARD #9846, #9873, #9877, #9884 (4 open)
AUTO-OWNR #9816, #9821, #9828, #9876 (4 open)
AUTO-REV-SUP #9832, #9869 (2 open)
AUTO-DOCS #9829, #9834 (2 open)
AUTO-WATCHDOG #9835, #9887 (2 open)
BUG-HUNT-POOL-SUPERVISOR #9764, #9780 (2 open)
AUTO-IMP-POOL #9680, #9761, #9867 (3 open)
AUTO-UAT-POOL #9682, #9718, #9769, #9833 (4 open)
AUTO-INF-POOL #9710, #9802 (2 open)
AUTO-HUMAN #9729, #9739, #9763, #9795 (4 open)

Expected Behavior

Each supervisor should close its previous tracking issue before creating a new one. Only ONE open tracking issue per supervisor prefix should exist at any time.

Impact

  • Makes it hard to find current supervisor status
  • Clutters the issue tracker with stale status issues
  • Violates the "No duplicate status tracking issues from the same agent prefix" rule

Each supervisor's tracking issue creation logic should:

  1. Search for existing open tracking issues with the same prefix
  2. Close all found issues before creating the new one
  3. Only then create the new tracking issue

Watchdog Actions Taken

  • Dispatched [AUTO-WDOG-3], [AUTO-WDOG-4], [AUTO-WDOG-5] to close duplicates
  • Workers launched but did not complete successfully (possible agent type configuration issue)
  • Escalating to human feedback for resolution

Automated by CleverAgents Bot
Supervisor: System Watchdog | Agent: system-watchdog-pool-supervisor


Automated by CleverAgents Bot
Agent: new-issue-creator

## Problem Multiple supervisors are creating new tracking issues each cycle without closing the previous ones. This results in dozens of open tracking issues per supervisor, making it impossible to find the current status. ## Affected Supervisors | Supervisor | Open Tracking Issues | |---|---| | AUTO-PRMRG-SUP | #9831, #9839, #9849, #9857, #9862, #9882, #9892 (7 open) | | AUTO-EPIC | #9840, #9843, #9850, #9861, #9868, #9879, #9896 (7 open) | | AUTO-EVLV | #9836, #9851, #9863, #9875 (4 open) | | AUTO-GUARD | #9846, #9873, #9877, #9884 (4 open) | | AUTO-OWNR | #9816, #9821, #9828, #9876 (4 open) | | AUTO-REV-SUP | #9832, #9869 (2 open) | | AUTO-DOCS | #9829, #9834 (2 open) | | AUTO-WATCHDOG | #9835, #9887 (2 open) | | BUG-HUNT-POOL-SUPERVISOR | #9764, #9780 (2 open) | | AUTO-IMP-POOL | #9680, #9761, #9867 (3 open) | | AUTO-UAT-POOL | #9682, #9718, #9769, #9833 (4 open) | | AUTO-INF-POOL | #9710, #9802 (2 open) | | AUTO-HUMAN | #9729, #9739, #9763, #9795 (4 open) | ## Expected Behavior Each supervisor should close its previous tracking issue before creating a new one. Only ONE open tracking issue per supervisor prefix should exist at any time. ## Impact - Makes it hard to find current supervisor status - Clutters the issue tracker with stale status issues - Violates the "No duplicate status tracking issues from the same agent prefix" rule ## Recommended Fix Each supervisor's tracking issue creation logic should: 1. Search for existing open tracking issues with the same prefix 2. Close all found issues before creating the new one 3. Only then create the new tracking issue ## Watchdog Actions Taken - Dispatched [AUTO-WDOG-3], [AUTO-WDOG-4], [AUTO-WDOG-5] to close duplicates - Workers launched but did not complete successfully (possible agent type configuration issue) - Escalating to human feedback for resolution --- **Automated by CleverAgents Bot** Supervisor: System Watchdog | Agent: system-watchdog-pool-supervisor --- **Automated by CleverAgents Bot** Agent: new-issue-creator
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#9904
No description provided.