Back to the guides

PRACTICAL SOFTWARE GUIDE

Todoist recurring tasks: test overdue rescheduling and skipped dates

Completing a manually rescheduled recurring task can calculate the next occurrence from the completion date and skip expected dates.

SOURCE-BASED ANALYSIS · NO HANDS-ON RATING

Distinguish overdue completion from manual rescheduling

Todoist advances a recurring task when it is completed. Its documentation warns that manually rescheduling an overdue recurring task and then completing it can calculate the next occurrence from the completion year or date, skipping occurrences between the original and rescheduled dates. Yearly work makes this boundary especially visible.

Build four recurrence fixtures

Use synthetic daily, weekly and yearly tasks. Record the expected next date before completing or rescheduling anything.

FixtureActionExpected check
Daily task completed lateComplete overdue occurrenceNext date follows recurrence rule
Weekly task rescheduledMove then completeSkipped dates identified
Yearly task moved monthsComplete in later yearNext year verified
Recurring task stoppedComplete foreverNo next occurrence

Protect milestone dates

If preparatory work must happen earlier without moving the main annual recurrence, Todoist recommends keeping the main task on its original date and using subtasks for earlier work. The Reset sub-tasks setting determines whether completed subtasks reappear on the next parent occurrence, so include it in the acceptance check.

  1. Write the recurrence expression and expected next three dates.
  2. Complete one overdue occurrence without rescheduling.
  3. Reschedule a separate fixture before completion.
  4. Compare the resulting next dates.
  5. Check whether subtasks reset as intended.
  6. Use Complete forever only for deliberate closure.
  7. Record the observed rule beside the operational task.

Accept a predictable calendar

Accept the schedule when normal, overdue and rescheduled cases all produce understood dates. Do not repair a missed occurrence by moving the only recurring record until the skipped-date consequence has been reviewed.

Sources and verification

Official documentation checked on 2026-10-29. Worked examples are hypothetical planning exercises, not measured product benchmarks.

Continue your evaluation

Practical guides for this topic

Put your tools to work.

Need help choosing or setting up your tools? Tell Koldia what you want to improve.

Discuss your project