[Bug]: Recurring tasks completed after scheduled date do not process into next available recurrence

[jpmoo]

What's the bug?

I have a recurring task (weekly for a specific day of the week) scheduled for yesterday.

Instead of completing it yesterday, I mark it complete in a list view today. A notification indicates that yesterday's instance is complete.

However, the task does not cycle to the next recurrence. The "complete-instances" property lists today's date, and the completion calendar in the edit modal shows a completion today, with yesterday's instance still "open." The scheduled date remains yesterday.

What did you expect to happen?

I expected the most recent recurrence (yesterday) to be marked complete on the calendar and in the "complete-instances" property, and for the scheduled date to advance to the next recurrence after today.

Which part of TaskNotes is affected?

Task Management

Screenshots or Screen Recordings

Technical Details (Optional)

No response

[callumalpass]

Thanks for reporting this @jpmoo--that's an interesting bug! I'll work on it :)

[jpmoo]

It works properly on the calendar view if I right-click and select "mark task complete for this date" regardless of today's date. It just doesn't seem to work properly by clicking complete (clicking the circle to cycle through the status options) on list or agenda views. Haven't tested kanban.

So, whatever's happening on calendar view needs to happen everywhere. :)

[stevennguyen]

To add more visibility, this is also happening in the Bases TaskNotes view. The completed_instances field is populated with the date of completion (which is after the scheduled date) and the next expected scheduled date is not populated in scheduled.

In the note view, I can click the status icon to complete the task in the task card which populates completed_instances with the scheduled date (and not the actual date of completion) but does update scheduled to the next expected date.

Thanks for all your great work on this plugin.

[martin-forge]

I've traced the root cause for this.

Where: TaskService.ts, toggleRecurringTaskComplete(task, date?) — when the date parameter is omitted, the method defaults to getTodayLocal() regardless of recurrence anchor type.

Why it matters for scheduled-anchor tasks: the outstanding occurrence is identified by task.scheduled. Completing the task late from a view that doesn't pass an explicit date records today in complete_instances instead of the scheduled occurrence date. The original occurrence stays "open" and scheduled may not advance correctly.

Why calendar view works (as @jpmoo noted): the right-click "mark task complete for this date" passes the occurrence date explicitly, bypassing the default.

Minimal fix: when date is omitted and recurrence_anchor !== "completion" and task.scheduled exists, default to the date part of task.scheduled instead of today. I have a working local fix and am preparing a PR.