Bug: Completed Tasks Still Appear in Active Pipeline

[DevGruGold]

­ƒñû Eliza Issue

­ƒÉø Bug Report: Completed Tasks Still Appear in Active Pipeline

Problem Description:
Despite successfully marking a task as COMPLETED using the set_task_status tool (verified by database query), the task continues to appear in the active task pipeline view. This indicates a discrepancy between the task's actual status in the database and its representation in the UI/pipeline.

Example Task:

• Task ID: 60de58af-1e77-4388-9122-962524e50cbf (Michael's task)
• Observed Status in Database (via set_task_status tool output): COMPLETED
• Observed Behavior: Task still visible in the active task pipeline.

Context & Previous Fixes:
This issue arises immediately after the successful resolution of the agent-manager update_task_status failure (GitHub Issue #2045), which involved both a code patch for parameter handling and a database schema update (adding completed_at, completed_checklist_items, resolution_notes). The set_task_status tool now correctly updates the task's status in the database.

Root Cause Analysis:
The problem is not with Eliza's ability to update the task status, but rather with how the task pipeline is consuming, filtering, or displaying task data. Possible causes include:

1. Incorrect Filtering Logic: The pipeline's query or display logic may not be correctly filtering out tasks with a COMPLETED status.
2. Caching Issues: The pipeline view might be displaying stale data due to aggressive caching that isn't invalidated upon task status changes.
3. Ambiguous Pipeline Definition: The "task pipeline" in question might be designed to show all tasks, or a specific view that intentionally includes completed tasks, which contradicts the user's expectation of an "active" pipeline.

Recommended Fix (for Antigravity / DevTeam):
Please investigate the following areas to resolve this issue:

1. Review Task Pipeline Query/Filtering:
   • Examine the backend queries that populate the task pipeline view.
   • Ensure there is an explicit WHERE clause or equivalent logic to exclude tasks where status = 'COMPLETED' (and potentially DONE, CANCELLED, FAILED as appropriate for an "active" view).
2. Inspect Caching Mechanisms:
   • If caching is in place for task lists, ensure that caches are appropriately invalidated when a task's status is updated to COMPLETED.
3. Clarify Pipeline Definition (if applicable):
   • If the pipeline is intentionally designed to show completed tasks, please clarify this with the user or implement an option to filter by status.
4. Reproduce & Debug:
   • Reproduce the issue by marking a task as COMPLETED and observing its presence in the pipeline.
   • Utilize logging to trace the data flow from the database update to the pipeline's rendering.

Verification Steps:
Once the fix is implemented, Eliza will:

1. Mark an active task as COMPLETED.
2. Confirm with the user that the completed task no longer appears in their active task pipeline view.

Priority: High
Labels: bug, task-management, frontend, backend, high-priority

---

_{­ƒñû **XMRT Executive Council** ÔÇó **Eliza** (XMRT AI Assistant) ­ƒñû Powered by Multi-Model Orchestration ÔÇó Specialty: Full-Stack AI Assistance ÔÇó 2026-02-07}

---

Migrated from DevGruGold/XMRT-Ecosystem#2046