Skip to content

fix: scheduler task UUID mismatch causing Task not found errors#1350

Open
Maxei6 wants to merge 2 commits intoagent0ai:mainfrom
Maxei6:fix-scheduler-uuid-mismatch
Open

fix: scheduler task UUID mismatch causing Task not found errors#1350
Maxei6 wants to merge 2 commits intoagent0ai:mainfrom
Maxei6:fix-scheduler-uuid-mismatch

Conversation

@Maxei6
Copy link
Copy Markdown

@Maxei6 Maxei6 commented Mar 28, 2026

Problem

Scheduler task operations fail with "Task not found" and "Failed to save task" errors due to UUID/ID field mismatch between frontend stores and backend API.

Changes

scheduler-store.js

  • Added context_id fallback in syncTasksFromSidebar() method

tasks-store.js

  • Fixed contains(): changed t?.id to t?.uuid
  • Fixed firstId(): changed this.tasks[0]?.id to this.tasks[0]?.uuid

Why

The sidebar passes tasks with id field, but the store was looking up by uuid. The backend API returns uuid, so all lookups should use uuid.

Maxei6 added 2 commits March 27, 2026 16:35
The modal header used grid-template-columns: 40fr 0.5fr which gave the close button only ~1.2% of the header width, making it effectively unclickable.

Changed to grid-template-columns: 1fr auto which gives the title flexible space while keeping the close button at its natural width.
Changed task ID field references from 'id' to 'uuid' to match backend:
- scheduler-store.js: Added context_id fallback in syncTasksFromSidebar
- tasks-store.js: Fixed contains() to use t?.uuid instead of t?.id
- tasks-store.js: Fixed firstId() to return this.tasks[0]?.uuid

This fixes the 'Failed to save task' and 'Task not found' errors.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant