App version: Claude desktop (Cowork) 1.12603.1, CCD 2.1.170, Windows 11 (build 10.0.26200)
Summary:
The Schedules panel in the sidebar displays "No scheduled tasks yet" even when a valid, enabled scheduled task exists, runs on its cron schedule, and is fully visible/manageable through the scheduled-tasks MCP tool. This affects both a pre-existing task and a brand-new task created fresh through the normal creation flow.
Steps to reproduce:
- Have (or create) a recurring scheduled task, e.g. via the
scheduled-tasks tool or the app's own schedule creation flow — cron 0 19 * * *.
- Confirm the task fires correctly: check
logs/main.log for [CCDScheduledTasks] Spawning new session for scheduled task ... and [CCDScheduledTasks] Confirmed task run for: ... — task runs as expected.
- Open the Scheduled section in the sidebar.
Expected: The task appears in the list with its schedule, enabled state, and next/last run time.
Actual: Panel shows "No scheduled tasks yet," regardless of:
- Whether the task predates or postdates the current app session
- Which project the task's
cwd is set to (tested with a task tied to the currently active project — still not shown)
- Full app restart (quit from tray, not just window close)
- Recreating the task from scratch via
create_scheduled_task rather than editing an existing one
What we confirmed is not the cause (data layer is healthy):
The task registry at AppData\Roaming\Claude\claude-code-sessions\<projectId>\<sessionId>\scheduled-tasks.json correctly reflects the task's state (id, cronExpression, enabled, filePath, cwd) at all times, matching what list_scheduled_tasks returns. Two backend log namespaces exist — [CCDScheduledTasks] (dispatch/execution — works correctly) and [ScheduledTasks] (appears tied to the UI) — both log Reset → Initialized with matching accountId/orgId on every app launch, but the panel never populates.
Suspected trigger: Started after some folders under this app's AppData directory were unexpectedly deleted (exact folders unknown — was not captured before deletion). The backend scheduler state survived (either regenerated or read from ~/.claude/scheduled-tasks/*/SKILL.md directly), but whatever the Schedules panel's UI-side data source is did not recover.
Impact: Users with this issue cannot view, edit, pause, or delete scheduled tasks from the UI at all — the only workaround is managing them via the scheduled-tasks MCP tool through a chat session.
App version: Claude desktop (Cowork) 1.12603.1, CCD 2.1.170, Windows 11 (build 10.0.26200)
Summary:
The Schedules panel in the sidebar displays "No scheduled tasks yet" even when a valid, enabled scheduled task exists, runs on its cron schedule, and is fully visible/manageable through the
scheduled-tasksMCP tool. This affects both a pre-existing task and a brand-new task created fresh through the normal creation flow.Steps to reproduce:
scheduled-taskstool or the app's own schedule creation flow — cron0 19 * * *.logs/main.logfor[CCDScheduledTasks] Spawning new session for scheduled task ...and[CCDScheduledTasks] Confirmed task run for: ...— task runs as expected.Expected: The task appears in the list with its schedule, enabled state, and next/last run time.
Actual: Panel shows "No scheduled tasks yet," regardless of:
cwdis set to (tested with a task tied to the currently active project — still not shown)create_scheduled_taskrather than editing an existing oneWhat we confirmed is not the cause (data layer is healthy):
The task registry at
AppData\Roaming\Claude\claude-code-sessions\<projectId>\<sessionId>\scheduled-tasks.jsoncorrectly reflects the task's state (id, cronExpression, enabled, filePath, cwd) at all times, matching whatlist_scheduled_tasksreturns. Two backend log namespaces exist —[CCDScheduledTasks](dispatch/execution — works correctly) and[ScheduledTasks](appears tied to the UI) — both logReset→Initializedwith matchingaccountId/orgIdon every app launch, but the panel never populates.Suspected trigger: Started after some folders under this app's AppData directory were unexpectedly deleted (exact folders unknown — was not captured before deletion). The backend scheduler state survived (either regenerated or read from
~/.claude/scheduled-tasks/*/SKILL.mddirectly), but whatever the Schedules panel's UI-side data source is did not recover.Impact: Users with this issue cannot view, edit, pause, or delete scheduled tasks from the UI at all — the only workaround is managing them via the
scheduled-tasksMCP tool through a chat session.