UAT: Plan.subplan_statuses and Plan.subplan_config are not persisted to the database — subplan orchestration state is lost on restart #2870

Closed
opened 2026-04-04 21:14:30 +00:00 by freemo · 2 comments
Owner

Transitioning issue state from State/Verified to State/In Progress per ticket lifecycle rules.

Labels updated accordingly.

Transitioning issue state from State/Verified to State/In Progress per ticket lifecycle rules. Labels updated accordingly.
freemo added this to the v3.7.0 milestone 2026-04-04 21:14:35 +00:00
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: High — Subplan orchestration state (subplan_statuses, subplan_config) is lost on restart. This breaks retry logic, parallel execution tracking, and parent-child plan relationships. The spec requires parent plans to track spawned subplan status.
  • Milestone: v3.7.0 (already set correctly)
  • MoSCoW: Should Have — Subplan persistence is required for reliable hierarchical plan execution. The spec requires subplan orchestration, and losing this state on restart breaks the retry and failure handling logic. However, this is part of the Subplans & Parallelism epic which is a Should Have for the current milestone.
  • Parent Epic: #368 (Epic: Subplans & Parallelism)

Valid UAT finding with clear reproduction steps. The missing database columns for subplan_config_json and subplan_statuses_json are a clear persistence gap. The fix requires an Alembic migration and model updates.


Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: ca-project-owner

Issue triaged by project owner: - **State**: Verified - **Priority**: High — Subplan orchestration state (`subplan_statuses`, `subplan_config`) is lost on restart. This breaks retry logic, parallel execution tracking, and parent-child plan relationships. The spec requires parent plans to track spawned subplan status. - **Milestone**: v3.7.0 (already set correctly) - **MoSCoW**: Should Have — Subplan persistence is required for reliable hierarchical plan execution. The spec requires subplan orchestration, and losing this state on restart breaks the retry and failure handling logic. However, this is part of the Subplans & Parallelism epic which is a Should Have for the current milestone. - **Parent Epic**: #368 (Epic: Subplans & Parallelism) Valid UAT finding with clear reproduction steps. The missing database columns for `subplan_config_json` and `subplan_statuses_json` are a clear persistence gap. The fix requires an Alembic migration and model updates. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
Owner

State label reconciliation:

  • Corrected to: State/Completed
  • Reason: Issue is closed but had a non-terminal state label (State/In Review, State/Verified, or State/In Progress). CONTRIBUTING.md requires closed issues to have State/Completed or State/Wont Do.

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: backlog-groomer

State label reconciliation: - Corrected to: `State/Completed` - Reason: Issue is closed but had a non-terminal state label (`State/In Review`, `State/Verified`, or `State/In Progress`). CONTRIBUTING.md requires closed issues to have `State/Completed` or `State/Wont Do`. --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#368 Epic: Subplans & Parallelism
cleveragents/cleveragents-core
Reference
cleveragents/cleveragents-core#2870
No description provided.