Similar titles are not proof of duplication
Two weekly review tasks may represent different periods. One may be an overdue occurrence and the other the next scheduled run. Compare the period, trigger, creation context and completion evidence. Do not use identical wording as the sole reason to remove one. A repeated task can be legitimate even when the earlier one is not finished.
Check the recurrence rule
Date, status and completion triggers can create different patterns. Nifty documents these choices, including date-based creation when the current task is unfinished. Review the configured behavior with an authorized owner. Do not change the rule merely to remove visible clutter without understanding which future occurrences the change will affect.
A fictional pair
Review-Week-40 is waiting for an answer; Review-Week-41 was created on schedule. They are not duplicates simply because both say review equipment list. The team may decide to consolidate the work, but that is a decision with a reason and an owner. Preserve the unresolved question and the relationship between the occurrences.
Use a non-destructive review first
Mark suspected duplicates for review or record the question in the approved process. Before deletion or merging, establish what history, comments and references would be lost and whether the action is reversible. This public guide does not authorize destructive account changes, and its local tools never modify a task system.
Preserve the unanswered question
Before consolidating two reviews, identify any unresolved question, comment or dependency attached to each occurrence. A later review may repeat most of the checklist while carrying a different period-specific decision. Record which occurrence retains the work and how the other is referenced if the authorized team chooses consolidation. The safe default during investigation is to preserve both records, not to delete one and hope that its context was copied elsewhere.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Nifty recurring tasks — Merchant documentation · help.niftypm.com · Merchant-controlled · checked 2026-10-01