Describe the bug
The Todoist New Completed Task source (todoist-completed-task) does not emit an event when a recurring task is marked done. Non-recurring (one-off) task completions still emit correctly, so the trigger looks like it works, but every recurring completion is silently missed.
To Reproduce
Reproduced live against the Todoist API v1 (verified 2026-07-14). Using an authenticated Todoist account:
- Create a recurring task:
POST /api/v1/tasks with {"content": "recurring test", "due_string": "every day"}. Response confirms due.is_recurring: true.
- Create a non-recurring control task:
POST /api/v1/tasks with {"content": "normal test"} (due: null).
- Complete both:
POST /api/v1/tasks/{id}/close for each.
- Re-fetch each task:
- Recurring (
GET /api/v1/tasks/{id}): checked: false, completed_at: null, completed_count: 1, and due.date has advanced to the next day. The task is NOT in a completed state — it was rescheduled.
- Control (
GET /api/v1/tasks/{id}): checked: true, completed_at set.
- Query the exact endpoint the source polls:
GET /api/v1/tasks/completed/by_completion_date?since=<today>&until=<tomorrow>.
- Result:
items contains only the control task. The recurring completion is absent, even though completed_count incremented.
- For completeness,
GET /api/v1/tasks/completed/by_due_date?since=...&until=... over the occurrence's due date also returns items: [] for the recurring completion.
Net: the recurring task was completed (Todoist recorded it), but it appears in neither v1 REST completed-task endpoint, so the source never emits it.
Expected behavior
Marking a recurring Todoist task as done should emit a "New Completed Task" event, matching the pre-v1-migration behavior.
Screenshots
N/A (verified via raw API responses; can attach the request/response bodies if helpful).
Additional context
Add any other context about the problem here.
Describe the bug
The Todoist New Completed Task source (
todoist-completed-task) does not emit an event when a recurring task is marked done. Non-recurring (one-off) task completions still emit correctly, so the trigger looks like it works, but every recurring completion is silently missed.To Reproduce
Reproduced live against the Todoist API v1 (verified 2026-07-14). Using an authenticated Todoist account:
POST /api/v1/taskswith{"content": "recurring test", "due_string": "every day"}. Response confirmsdue.is_recurring: true.POST /api/v1/taskswith{"content": "normal test"}(due: null).POST /api/v1/tasks/{id}/closefor each.GET /api/v1/tasks/{id}):checked: false,completed_at: null,completed_count: 1, anddue.datehas advanced to the next day. The task is NOT in a completed state — it was rescheduled.GET /api/v1/tasks/{id}):checked: true,completed_atset.GET /api/v1/tasks/completed/by_completion_date?since=<today>&until=<tomorrow>.itemscontains only the control task. The recurring completion is absent, even thoughcompleted_countincremented.GET /api/v1/tasks/completed/by_due_date?since=...&until=...over the occurrence's due date also returnsitems: []for the recurring completion.Net: the recurring task was completed (Todoist recorded it), but it appears in neither v1 REST completed-task endpoint, so the source never emits it.
Expected behavior
Marking a recurring Todoist task as done should emit a "New Completed Task" event, matching the pre-v1-migration behavior.
Screenshots
N/A (verified via raw API responses; can attach the request/response bodies if helpful).
Additional context
Add any other context about the problem here.