A fresh weekly task appears, but its Done checkbox is already checked. Or the page looks unfinished while every checklist item is ticked.
Inspect the template that creates the task before repeatedly resetting individual records. The database completion field and the checklist in the page body are two separate places to check.
1. Confirm the actual symptom
Find one affected occurrence in an unfiltered Table view of the source database. Open the page and record its initial values.
| Symptom | First check |
|---|---|
| Done is checked | Completion property in the creation template |
| Status says Complete | Template’s starting Status value |
| Body checklist is ticked | To-do blocks inside the template body |
Do not conclude that a filtered-out task was never created. A completed record may simply be excluded from your active view.
2. Open the template, not just its generated task
- Open the dropdown beside New in the source database.
- Find the template used for this routine.
- Open its options and choose Edit.
- Check the completion property.
- Check the page body’s checklist separately.
Notion’s database template documentation explains template properties and repeating copies. A normal generated task is a separate record from its starting template.
3. Set an intentional starting state
For a routine that should begin unfinished, leave Done unchecked or select your existing starting Status. Preserve the completion system your database already uses.
Reset body checklist items that each occurrence should perform again. Keep reference text and genuinely permanent instructions intact.
A page-body checkbox does not automatically update the database completion property in this recipe. If your workspace connects them through custom mechanisms, inspect those separately.
4. Create a manual test occurrence
- Leave the template editor.
- Create a fictional task explicitly using that template.
- Inspect its completion property before editing.
- Open its body and check the to-do blocks.
- Confirm it appears in the intended active view.
Call the record Template check — fictional so it is not confused with real work.
This tests the template’s starting content. It does not prove the repeating schedule has run. For scheduling, use the recurring task setup guide.
5. If the manual result is correct, inspect the other inputs
Confirm the scheduled routine uses the same template you tested. Review other mechanisms that change properties after creation, if any exist in your workspace.
Also check whether your normal creation view differs from the unfiltered test context. Record the observed difference rather than changing several settings at once.
If the task starts in the right state but disappears after an edit, follow the task visibility guide.
6. Repair old occurrences individually
Changing the template does not establish that past occurrences are now correct. Review the affected dates and the actual work performed.
Do not bulk-uncheck every record: some routines may genuinely have been completed. Correct only mistaken completion states and retain useful notes about what happened.
Recurring project assignments also need review. A fixed project may be intentional, but the wrong-project template guide helps identify an obsolete selection.
Common mistakes
- Resetting one generated task while leaving the template unchanged.
- Checking the body checklist but ignoring the database Status.
- Treating a manual template test as proof that scheduling works.
- Reopening genuinely completed historical work in a bulk cleanup.
Frequently asked questions
Does finishing one occurrence mean all future ones should be complete?
No. Each occurrence should start in the state defined by its creation process. Inspect the template if new records arrive complete.
Will resetting one task fix the template?
No. Edit the database template separately from the occurrence created with it.
Why are the checklist and Status different?
They are separate elements in this recipe. The page body checklist does not automatically define the database completion field.
Does the manual test check the repeating schedule?
No. It checks the template’s starting content; the schedule needs its own observed occurrence.
Should I reopen all old occurrences?
No. Review what was actually completed and correct only mistaken records.
Explore the wider workflow
You can build this process in your existing workspace. For a broader client and project system, explore Freelancer CRM and compare its structure with your workflow.