Parked agent jobs remain visible indefinitely, but the task-management interface currently exposes no action to close or archive them. This leaves stale jobs in the active job history and requires manual cleanup outside the normal workflow.
Observed behavior
The following old jobs are parked and cannot be closed through the available task-management actions:
Job #1 — daemon: label dispatch trigger with empty label matches every open issue
Job #2 — archied: [[repos]] entries can't span more than one forge
The interface can list and inspect parked jobs, but provides no close/archive operation.
Expected behavior
Provide an explicit operation for a parked job, such as:
close when the job is definitively finished or no longer actionable;
archive when it should be removed from the active job list while retaining history;
optionally reopen if a parked job needs to be resumed.
The operation should persist the state, be reflected in task listings, and retain the job logs and audit history.
Acceptance criteria
A user can close or archive a parked job from the supported task-management interface/API.
The operation is idempotent and reports a clear error for invalid state transitions.
Closed/archived jobs no longer appear among active or parked jobs by default, while remaining queryable.
Existing logs, attempts, and failure details remain accessible.
Tests cover closing, archiving, reopening (if supported), and repeated operations.
Close reason
Already implemented and in use: parked tasks expose Retry/Abandon/Reject — Abandon/Reject transition to terminal Won't-do and close the forge issue; terminal tasks then expose Archive (removes the row, keeps the durable audit event); Retry reopens parked work. Landed in de60802 (archive+retry controls) and 52bb018 (reject from every non-terminal state incl. parked); covered by TestLifecycleSpecificTaskActions, TestTaskListExposesLifecycleActions, TestArchiveRemovesOnlyOneTerminalTask.
Imported from beads archie-core-1787583419901-1-85796c0b · GitHub #624 · type bug · priority P2 · created 2026-08-24 · closed 2026-09-02
## Problem
Parked agent jobs remain visible indefinitely, but the task-management interface currently exposes no action to close or archive them. This leaves stale jobs in the active job history and requires manual cleanup outside the normal workflow.
## Observed behavior
The following old jobs are parked and cannot be closed through the available task-management actions:
- Job #1 — `daemon: label dispatch trigger with empty label matches every open issue`
- Job #2 — `archied: [[repos]] entries can't span more than one forge`
The interface can list and inspect parked jobs, but provides no close/archive operation.
## Expected behavior
Provide an explicit operation for a parked job, such as:
- `close` when the job is definitively finished or no longer actionable;
- `archive` when it should be removed from the active job list while retaining history;
- optionally `reopen` if a parked job needs to be resumed.
The operation should persist the state, be reflected in task listings, and retain the job logs and audit history.
## Acceptance criteria
- A user can close or archive a parked job from the supported task-management interface/API.
- The operation is idempotent and reports a clear error for invalid state transitions.
- Closed/archived jobs no longer appear among active or parked jobs by default, while remaining queryable.
- Existing logs, attempts, and failure details remain accessible.
- Tests cover closing, archiving, reopening (if supported), and repeated operations.
### Close reason
Already implemented and in use: parked tasks expose Retry/Abandon/Reject — Abandon/Reject transition to terminal Won't-do and close the forge issue; terminal tasks then expose Archive (removes the row, keeps the durable audit event); Retry reopens parked work. Landed in de60802 (archive+retry controls) and 52bb018 (reject from every non-terminal state incl. parked); covered by TestLifecycleSpecificTaskActions, TestTaskListExposesLifecycleActions, TestArchiveRemovesOnlyOneTerminalTask.
---
_Imported from beads `archie-core-1787583419901-1-85796c0b` · GitHub #624 · type bug · priority P2 · created 2026-08-24 · closed 2026-09-02_
sam
added the mediumbug labels 2026-10-27 13:38:35 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
Parked agent jobs remain visible indefinitely, but the task-management interface currently exposes no action to close or archive them. This leaves stale jobs in the active job history and requires manual cleanup outside the normal workflow.
Observed behavior
The following old jobs are parked and cannot be closed through the available task-management actions:
daemon: label dispatch trigger with empty label matches every open issuearchied: [[repos]] entries can't span more than one forgeThe interface can list and inspect parked jobs, but provides no close/archive operation.
Expected behavior
Provide an explicit operation for a parked job, such as:
closewhen the job is definitively finished or no longer actionable;archivewhen it should be removed from the active job list while retaining history;reopenif a parked job needs to be resumed.The operation should persist the state, be reflected in task listings, and retain the job logs and audit history.
Acceptance criteria
Close reason
Already implemented and in use: parked tasks expose Retry/Abandon/Reject — Abandon/Reject transition to terminal Won't-do and close the forge issue; terminal tasks then expose Archive (removes the row, keeps the durable audit event); Retry reopens parked work. Landed in de60802 (archive+retry controls) and 52bb018 (reject from every non-terminal state incl. parked); covered by TestLifecycleSpecificTaskActions, TestTaskListExposesLifecycleActions, TestArchiveRemovesOnlyOneTerminalTask.
Imported from beads
archie-core-1787583419901-1-85796c0b· GitHub #624 · type bug · priority P2 · created 2026-08-24 · closed 2026-09-02