Recurring Tasks

A recurring task is some periodic and atomic unit of work. Recurring tasks live in the "recurring tasks" view, but they're instantiated as regular tasks in the "inbox". A recurring task is ideal to model work which needs to be done periodically, like a chore or a habit.

For example, you can have a recurring task like "Clean out AC filters every week", or "Pay home insurance every month", or "Walk more than 10000 steps every day".

In the recurring tasks view, the task templates might look like this:

Recurring tasks templates

Recurring Tasks Properties

Recurring tasks have a period and a period interval. The former is set via the period property and the latter is derived uniquely from this. The period can be one of:

Notice that the smallest period is the daily one, with a period interval of one day. In general, for a given period interval there can be only one instantiation of a task of that period.

While in the inbox, the instantiated tasks might look like this - notice the "Weekly" and "Monthly" labels:

Inbox with recurring tasks

The instantiated task in the inbox is constructed from the recurring task template, but it also changes in the following way:

Recurring tasks can also have an actionable date. By default there is none, and the generated inbox task won't have an actionable date. If you specify an actionable_from_day and/or actionable_from_month properties, they will determine the inbox tasks to have one. They work like so:

Recurring tasks also have a deadline. By default the deadline is the end day of the period interval, at midnight. You can override it however to specify, via the due_at_day and due_at_time properties. They work like so:

In Notion an instantiated task might look like this then:

Instantiated recurring task image

Recurring tasks can be configured to skip certain periods via a skip rule. This is specified via the skip_rule property, which can be one of:

A recurring task can be mark as "must do", via the Must Do property. Being marked as such that will cause it to ignore vacations. For example, paying rent or taking some medicine can't be interrupted by a vacation.

A recurring task can also have an active interval. This is a time interval in which tasks should be generated. By default the interval is "empty", so inbox tasks are always generated. But by specifying either a start or an end to this interval, you can control when exactly tasks are generated. The rule is that the period interval for an inbox tasks intersects successfully the active interval.

A recurring task can be suspended, via the Suspended property. Being marked as such means that the task won't be generated at all. For example, going to the gym might be suspended while you're recovering from an illness.

A recurring task can also have a difficulty, just like a regular task. This will be copied to all the instantiated tasks that are created.

Similarly, a recurring task can have the Eisenhower properties. These will be copied to all the instantiated tasks that are created.

Recurring tasks are created via the jupiter gen command. This has some special forms too:

Recurring tasks interact with vacations too. More precisely, if a task's period interval is fully contained within a vacation, that task won't be instantiated in the inbox via jupiter gen. For example, if you have a vacation from Monday 2020-02-09 to Sunday 2020-02-15, then all daily and weekly tasks for that week won't be created, but all monthly, quarterly and yearly ones will.

The jupiter gen command is idempotent, as described above. Furthermore it does not affect task status, or any extra edits on a particular instance of a task. If any property of the recurring task template which get copied over to the instance is modified, then the command will take care to update the instance too. Only archived and removed tasks are regenerated.

Recurring Tasks Interactions Summary

You can: