Notion FINALLY Made Recurring Tasks Work.
Based on Thomas Frank Explains's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Store recurrence rules in database properties (at minimum recur interval and due date) so Notion can compute the next schedule automatically.
Briefing
Notion’s new native recurring tasks support can now automatically push due dates forward when a task is marked complete—without relying on external apps like Todoist or TickTick. The core setup pairs a “recur interval” field (how far to move the due date) with an automation (or a button) that runs when task status changes to done, then uses a date-add formula to calculate the next due date and resets status so the task can be checked off again.
The simplest implementation starts with a tasks database that includes at least a due date and a status. To make recurrence work, an additional property—typically a number called “recur interval”—stores how many days to add after completion. A button-based approach can work on free plans: clicking a “complete” button triggers an action that edits the due date using Notion’s dateAdd function and the task’s own recur interval value. For more “native” behavior, automations are the next step: when status is set to complete, an automation edits the due date to the next scheduled date and changes status back to not started.
A key limitation appears immediately: non-recurring tasks would also get reset unless the automation is scoped. The fix is to create a filtered view (e.g., only tasks with a due date and a recur interval of at least 1) and configure the automation to trigger only for pages inside that recurring view. With that guardrail, tasks that aren’t meant to repeat can remain done permanently.
The next challenge is calendar reality. A naive “add 31 days” approach breaks on months with fewer days. To handle this, the setup evolves from a fixed “days” unit to a dynamic “recur unit” property (days, weeks, months, years). The automation then uses the recur unit value as the unit argument to dateAdd, including a formula trick to normalize the unit text into the exact lowercase format Notion expects. This enables robust monthly and quarterly schedules, such as shifting a “review monthly budget” task to the correct next month even when the day count varies.
For advanced recurrence—like “every Monday/Wednesday/Friday,” “last weekday of the month,” or “first weekday”—the workflow shifts from building complex logic inside each automation to using prebuilt formulas and template-ready properties. The template approach adds extra recur-unit options (e.g., months on the first weekday, last weekday, last day) plus a multi-select “days” property for specific weekdays. A crucial improvement is computing a “next due” formula inside the database, then having the automation simply set the canonical task’s due date to triggerPage.nextDue. That keeps the automation lean and makes upcoming schedules visible at a glance.
Finally, task history turns recurrence into habit tracking and compliance-friendly auditing. A “completed” timestamp property records when each occurrence was finished, while a self-referential relation (“occurrences”) links each historical instance back to a canonical recurring task. When the canonical task is completed, an automation creates a new page in the same tasks database as a historical record, copies relevant properties, sets its status to done, and relates it back to the canonical task. The result is a task history list, table, and chart view that shows when each occurrence was due and when it was actually completed—turning recurring tasks into a measurable timeline.
Cornell Notes
Native recurring tasks in Notion work by combining a recurrence rule (like a “recur interval”) with an automation that fires when status changes to done. The automation calculates the next due date using dateAdd and then resets status so the task can be checked off again. To prevent one-time tasks from being affected, the automation is restricted to a filtered “recurring” view (e.g., tasks with a due date and recur interval). Calendar edge cases are handled by adding a “recur unit” property (days/weeks/months/years) and normalizing its value for dateAdd. For richer schedules and history tracking, templates add advanced recur units (first/last weekday, specific weekdays) and create separate historical pages linked back to a canonical recurring task, enabling charts and audit trails.
How does Notion calculate the next due date when a recurring task is completed?
Why is a filtered view necessary, and what does it protect against?
How do recurrence rules avoid breaking on months with fewer than 31 days?
What’s the advantage of computing “next due” as a database formula instead of embedding logic in the automation?
How does task history work without losing the original recurring task logic?
Review Questions
- What properties and triggers are required for the simplest recurring-task automation in Notion?
- How does the filtered recurring view prevent one-time tasks from being reset?
- In the task-history setup, what role do the “occurrences” relation and the “completed” timestamp play?
Key Points
- 1
Store recurrence rules in database properties (at minimum recur interval and due date) so Notion can compute the next schedule automatically.
- 2
Use an automation triggered by status changing to done, then edit the due date with dateAdd and reset status back to not started.
- 3
Scope automations to a filtered recurring view (e.g., recur interval ≥ 1 and due date not empty) to avoid breaking one-time tasks.
- 4
Handle month-length variability by adding a dynamic recur unit (days/weeks/months/years) and normalizing its value for dateAdd.
- 5
For advanced schedules, compute next due as a formula property and let the automation simply apply triggerPage.nextDue.
- 6
Implement task history by creating separate historical pages linked back to a canonical recurring task through a self-referential relation (occurrences).
- 7
Use completed timestamps plus list/table/chart views to turn recurring tasks into measurable habit tracking or audit trails.